New issue
Advanced search Search tips

Issue 831495 link

Starred by 2 users

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Crash at shutdown in OnConnectionDisconnectedFilter

Reported by olivier....@canonical.com, Apr 11 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/66.0.3359.81 Chrome/66.0.3359.81 Safari/537.36

Steps to reproduce the problem:
This issue is being reported several times a week in the ubuntu bug tracker against the chromium-browser package (see https://launchpad.net/bugs/1729963 and all its duplicates). It looks like what's happening most frequently is the user shuts down their computer while chromium is running, which terminates the d-bus service, and causes chromium to crash as it doesn't expect the bus to disappear under its feet like that.

What is the expected behavior?
Chromium should gracefully handle the sudden disappearance of the bus instead of crashing.

What went wrong?
Chromium crashes when shutting down computer.

The earliest report of that crash in Ubuntu is with version 47.0.2526.73, the most recent is with version 65.0.3325.181. It happens across all supported versions of Ubuntu (14.04, 16.04, 17.10 and the upcoming 18.04).

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 65.0.3325.181  Channel: stable
OS Version: Ubuntu 18.04
Flash Version:
 
Stack trace:

#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
        set = {__val = {0, 139822897025744, 139818365353985, 0, 0, 9467692890123378432, 1, 139820043301445, 139821016944400, 3, 0, 108, 139821016944360, 139822897026859, 139821016944160, 139821016944128}}
        pid = <optimized out>
        tid = <optimized out>
#1  0x00007f2b1150ff5d in __GI_abort () at abort.c:90
        save_stage = 2
        act = {__sigaction_handler = {sa_handler = 0x7f2b118b2640 <_IO_2_1_stderr_>, sa_sigaction = 0x7f2b118b2640 <_IO_2_1_stderr_>}, sa_mask = {__val = {95, 139820043288768, 95, 3432, 139822951146712, 95, 493921239773, 96, 139822954653248, 95, 139820043288768, 1, 95, 139822954636256, 139822951097627, 139821016945760}}, sa_flags = 294331968, sa_restorer = 0x7f2b118ae3e0 <_IO_file_jumps>}
        sigs = {__val = {32, 0 <repeats 15 times>}}
#2  0x0000560314d25745 in base::debug::BreakDebugger() () at ../../base/debug/debugger_posix.cc:258
No locals.
#3  0x0000560314d3c5b0 in ~LogMessage () at ../../base/logging.cc:842
No locals.
#4  0x0000560315da09d4 in OnConnectionDisconnectedFilter () at ../../dbus/bus.cc:1151
No locals.
#5  0x00007f2b0e1b65c9 in dbus_connection_dispatch (connection=0x7f2a6402cea0) at ../../../dbus/dbus-connection.c:4705
        filter = <optimized out>
        next = 0x7f2ae40029d8
        message = 0x7f2ae4004fa0
        link = <optimized out>
        reply_serial = <optimized out>
        filter_list_copy = 0x7f2ae4002a20
        status = <optimized out>
        found_object = 236669241
        message_link = 0x7f2ae4002a38
        result = DBUS_HANDLER_RESULT_NOT_YET_HANDLED
        pending = <optimized out>
        connection = 0x7f2a6402cea0
        status = <optimized out>
#6  0x0000560315da1799 in dbus::Bus::ProcessAllIncomingDataIfAny() () at ../../dbus/bus.cc:781
No locals.
#7  0x0000560314d2747f in Run () at ../../base/callback.h:65
No locals.
#8  RunTask () at ../../base/debug/task_annotator.cc:55
No locals.
#9  0x0000560314d7e2ca in RunOrSkipTask () at ../../base/task_scheduler/task_tracker.cc:420
No locals.
#10 0x0000560314d7ed34 in base::internal::TaskTrackerPosix::RunOrSkipTask(base::internal::Task, base::internal::Sequence*, bool) () at ../../base/task_scheduler/task_tracker_posix.cc:23
No locals.
#11 0x0000560314d7daf4 in RunNextTask () at ../../base/task_scheduler/task_tracker.cc:322
No locals.
#12 0x0000560314dbf40b in ThreadMain () at ../../base/task_scheduler/scheduler_worker.cc:72
No locals.
#13 0x0000560314d879fd in ThreadFunc () at ../../base/threading/platform_thread_posix.cc:75
No locals.
#14 0x00007f2b11f017fc in start_thread (arg=0x7f2a9e0c2700) at pthread_create.c:465
        pd = 0x7f2a9e0c2700
        now = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139821016950528, -2464536035657934090, 140730793837838, 140730793837839, 139821016950528, 139821016951232, 2565091979878046454, 2565387576591882998}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
        not_first_call = <optimized out>
        pagesize_m1 = <optimized out>
        sp = <optimized out>
        freesize = <optimized out>
        __PRETTY_FUNCTION__ = "start_thread"
#15 0x00007f2b115ebb5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Cc: kkaluri@chromium.org
Components: Internals>Network>Filters
Labels: Needs-Feedback
olivier.tilloy@ Could you please help us with the 16 digit crash id from chrome://crashes for further triage
There's no crash id as this is the ubuntu chromium package, not chrome.
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 12 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: -Internals>Network>Filters
Labels: TE-NeedsTriageHelp
Unable to test this issue from TE-End, hence adding TE-NeedsTriageHelp for further triage.
Components: Internals>Core
Crash in dbus callbacks.
This is by far the most reported crash in chromium on Ubuntu (several duplicate reports a week, see https://launchpad.net/bugs/1729963). Any chance this can get a higher priority, at least to understand what's going on?
I'm wondering why dbus_connection_set_exit_on_disconnect (..., false) is used to not exit chromium when the dbus connection is lost and instead chromium is manually aborted in the OnConnectionDisconnectedFilter handler.

Sign in to add a comment