Closed
Bug 1376144
Opened 7 years ago
Closed 7 years ago
All tabs always crash with: cannot send/recv, SinkInfo contains invalid flags
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1375873
People
(Reporter: post+mozilla, Unassigned)
Details
Firefox Nightly "Version 56.0a1 (2017-06-24) (64-bit)" Linux moved itself into an entirely broken state -- when I open a new tab and go to a website, it just shows "Your tab just crashed.". When I click "Restore", the tab crashes immediately again. All my existing tabs that got restored when FF launches show the same behavior.
How I got here:
* Firefox Nightly was running just fine.
* Then my machine froze, I had to use Magic SysRQ to hard-reboot it.
* After coming back from the reboot, nightly behaves as described above.
I launched nightly on the console, setting RUST_BACKTRACE=1, and it shows this (excerpt):
```
###!!! [Parent][MessageChannel] Error: (msgtype=0x280080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x460040,name=PContent::Msg_LoadProcessScript) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x460101,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x460101,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv
thread '<unnamed>' panicked at 'SinkInfo contains invalid flags', /checkout/src/libcore/option.rs:794
stack backtrace:
thread '<unnamed>' panicked at 'SinkInfo contains invalid flags', /checkout/src/libcore/option.rs:794
stack backtrace:
thread '<unnamed>' panicked at 'SinkInfo contains invalid flags', /checkout/src/libcore/option.rs:794
stack backtrace:
thread '<unnamed>' panicked at 'SinkInfo contains invalid flags', /checkout/src/libcore/option.rs:794
stack backtrace:
0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
1: std::panicking::default_hook::{{closure}}
2: std::panicking::rust_panic_with_hook
3: std::panicking::begin_panic
4: std::panicking::begin_panic_fmt
5: core::panicking::panic_fmt
6: core::option::expect_failed
7: pulse::context::Context::get_sink_info_by_name::wrapped
8: <unknown>
9: <unknown>
10: pa_pdispatch_run
11: <unknown>
12: <unknown>
13: <unknown>
14: pa_mainloop_dispatch
15: pa_mainloop_iterate
16: pa_mainloop_run
17: <unknown>
18: <unknown>
19: start_thread
20: __clone
Redirecting call to abort() to mozalloc_abort
[Parent 11] WARNING: pipe error (106): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[Parent 11] WARNING: pipe error (103): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[Parent 11] WARNING: pipe error (101): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
###!!! [Parent][MessageChannel] Error: (msgtype=0x280080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
1: std::panicking::default_hook::{{closure}}
2: std::panicking::rust_panic_with_hook
3: std::panicking::begin_panic
4: std::panicking::begin_panic_fmt
5: core::panicking::panic_fmt
6: core::option::expect_failed
7: pulse::context::Context::get_sink_info_by_name::wrapped
8: <unknown>
9: <unknown>
10: pa_pdispatch_run
11: <unknown>
12: <unknown>
13: <unknown>
14: pa_mainloop_dispatch
15: pa_mainloop_iterate
16: pa_mainloop_run
17: <unknown>
18: <unknown>
19: start_thread
20: __clone
Redirecting call to abort() to mozalloc_abort
0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
1: std::panicking::default_hook::{{closure}}
2: std::panicking::rust_panic_with_hook
3: std::panicking::begin_panic
4: std::panicking::begin_panic_fmt
5: core::panicking::panic_fmt
6: core::option::expect_failed
7: pulse::context::Context::get_sink_info_by_name::wrapped
8: <unknown>
9: <unknown>
10: pa_pdispatch_run
11: <unknown>
12: <unknown>
[Parent 11] WARNING: pipe error (113): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
13: <unknown>
14: pa_mainloop_dispatch
15: pa_mainloop_iterate
16: pa_mainloop_run
17: <unknown>
18: <unknown>
19: start_thread
20: __clone
Redirecting call to abort() to mozalloc_abort
[Parent 11] WARNING: pipe error (128): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[Parent 11] WARNING: pipe error (126): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
1: std::panicking::default_hook::{{closure}}
2: std::panicking::rust_panic_with_hook
3: std::panicking::begin_panic
4: std::panicking::begin_panic_fmt
5: core::panicking::panic_fmt
6: core::option::expect_failed
7: pulse::context::Context::get_sink_info_by_name::wrapped
8: <unknown>
9: <unknown>
10: pa_pdispatch_run
11: <unknown>
12: <unknown>
13: <unknown>
14: pa_mainloop_dispatch
15: pa_mainloop_iterate
16: pa_mainloop_run
17: <unknown>
18: <unknown>
19: start_thread
20: __clone
Redirecting call to abort() to mozalloc_abort
[Parent 11] WARNING: pipe error (133): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[Parent 11] WARNING: pipe error (118): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[Parent 11] WARNING: pipe error (116): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[Parent 11] WARNING: pipe error (127): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[Parent 11] WARNING: pipe error (134): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[Parent 11] WARNING: pipe error (132): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[Parent 11] WARNING: pipe error (98): Connection reset by peer: file /home/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
###!!! [Parent][MessageChannel] Error: (msgtype=0x280080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x28006F,name=PBrowser::Msg_SynthMouseMoveEvent) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x280080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x280080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x460020,name=PContent::Msg_DataStoragePut) Channel error: cannot send/recv
```
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•