If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

50.0a1 Nightly crash on loading non-about: pages

RESOLVED DUPLICATE of bug 1286324

Status

()

Core
Security: Process Sandboxing
RESOLVED DUPLICATE of bug 1286324
a year ago
a year ago

People

(Reporter: kolubat, Unassigned)

Tracking

({crash})

50 Branch
crash
Points:
---

Firefox Tracking Flags

(e10s-)

Details

(Whiteboard: sb?)

(Reporter)

Description

a year ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20160708004052

Steps to reproduce:

Open Firefox Nightly 50.0a1 with --safe-mode and --no-remote and a clean profile.


Actual results:

Whenever loading any(?) HTTP(S) page other than about: pages, the tabs crash. Crash report: https://crash-stats.mozilla.com/report/index/8d2f63e8-d999-4652-89fb-fafad2160708

Example terminal output:

$ ./firefox --no-remote -P --safe-mode

(firefox:30280): Gtk-WARNING **: Theme directory actions/48 of theme breeze has no size field


(firefox:30280): Gtk-WARNING **: Theme directory categories/16 of theme breeze has no size field


(firefox:30280): Gtk-WARNING **: Theme directory categories/22 of theme breeze has no size field


(firefox:30280): Gtk-WARNING **: Theme directory categories/48 of theme breeze has no size field


(firefox:30280): Gtk-WARNING **: Theme directory devices/48 of theme breeze has no size field


(firefox:30280): Gtk-WARNING **: Theme directory actions/48 of theme breeze has no size field


(firefox:30280): Gtk-WARNING **: Theme directory categories/16 of theme breeze has no size field


(firefox:30280): Gtk-WARNING **: Theme directory categories/22 of theme breeze has no size field


(firefox:30280): Gtk-WARNING **: Theme directory categories/48 of theme breeze has no size field


(firefox:30280): Gtk-WARNING **: Theme directory devices/48 of theme breeze has no size field

Sandbox: seccomp sandbox violation: pid 30840, syscall 56, args 18874385 0 0 139810423676432 30840 139810423675712.  Killing process.
[Parent 30280] WARNING: pipe error (84): Connection reset by peer: file /builds/slave/m-cen-l64-ntly-000000000000000/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 320
[Parent 30280] WARNING: pipe error (61): Connection reset by peer: file /builds/slave/m-cen-l64-ntly-000000000000000/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 320

###!!! [Parent][MessageChannel] Error: (msgtype=0x2C007D,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv


###!!! [Parent][MessageChannel] Error: (msgtype=0x2C007D,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv

aSandbox: seccomp sandbox violation: pid 31866, syscall 56, args 18874385 0 0 140653032259088 31866 140653032258368.  Killing process.
[Parent 30280] WARNING: pipe error (88): Connection reset by peer: file /builds/slave/m-cen-l64-ntly-000000000000000/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 320

###!!! [Parent][MessageChannel] Error: (msgtype=0x2C007D,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv





Expected results:

Pages load
(Reporter)

Comment 1

a year ago
Bug doesn't occur with e10s disabled.

Updated

a year ago
Keywords: crash
tracking-e10s: --- → ?

Comment 2

a year ago
Hello Kolubat, I was unable to reproduce the crash with fresh profile, safe mode and e10s enabled on any HTTPS page. 

Tested on:
Version 	50.0a1
Build ID 	20160711034039
User Agent 	Mozilla/5.0 (X11; Linux i686; rv:50.0) Gecko/20100101 Firefox/50.0

Thanks for providing crash report.
e10s flag is set and I hope someone would look into this soon.
(In reply to kolubat from comment #0)
> Sandbox: seccomp sandbox violation: pid 30840, syscall 56, args 18874385 0 0
> 139810423676432 30840 139810423675712.  Killing process.

This looks relevant.
Component: Untriaged → Security: Process Sandboxing
Product: Firefox → Core

Updated

a year ago
tracking-e10s: ? → -
Whiteboard: sb?
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1286324
You need to log in before you can comment on or make changes to this bug.