Closed Bug 1285920 Opened 9 years ago Closed 9 years ago

Crash with wasm AngryBots demo (pulseaudio?) while seccomp-bpf for content is enabled on linux

Categories

(Core :: Security: Process Sandboxing, defect)

Product:
Core
Component:
Security: Process Sandboxing
Platform:
Unspecified
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1285507

People

(Reporter: stebs, Unassigned)

References

Details

Set javascript.options.wasm to true Crash with wasm AngryBots demo: http://webassembly.github.io/demo/AngryBots/ bp-03bd6d2e-84d5-4bf0-87a0-b45d92160711 Does not happen while security.sandbox.content.level set to 0 Build ID 20160710030217 User Agent Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 OS Linux 4.4.14-3-MANJARO
Blocks: 1280415
Summary: Crash with wasm Angry Bots demo (pulseaudio?) while seccomp-bpf for content is enabled on linux → Crash with wasm AngryBots demo (pulseaudio?) while seccomp-bpf for content is enabled on linux
Maybe same Bug?: bp-ddaffe06-fc11-4ecb-a113-312402160711 If yes, it's unrelated to wasm, since this time it was disabled. Happened with Simple mozRTCPeerConnection Video Test https://mozilla.github.io/webrtc-landing/pc_test.html
Both crash reports are related to the same system call that is not whitelisted yet. Bug 1285507 contains the patch to whitelist sys_memfd_create (the system call in question). The patch is currently on inbound and should be merged to m-c soon.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Can confirm fixed for both usecases with Build ID 20160712030234, thanks!
You need to log in before you can comment on or make changes to this bug.