New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 616755 link

Starred by 1 user
Status: WontFix
Owner:
hashimoto@chromium.org
Closed: Feb 2017
Cc:
derat@chromium.org
█ hdodda@chromium.org
jsb...@chromium.org
█ msrchandra@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Chrome crashes after waking laptop and trying to play music through Google Play Music

Project Member Reported by elil@google.com, Jun 2 2016 
IMPORTANT: Your crash has already been automatically reported to our crash system. Please file this bug only if you can provide more information about it.


Chrome Version: 51.0.2704.79
Operating System: Linux 4.2.0-36-generic

URL (if applicable) where crash occurred:

Can you reproduce this crash?

What steps will reproduce this crash? (If it's not reproducible, what were you doing just before the crash?)
1. Unlocked laptop
2. Tried to play music with Google Play Music via browser
3. Attempted to play test sound via Cinnamon sound settings, but no sound playing

****DO NOT CHANGE BELOW THIS LINE****
Crash ID: crash/f0fd965a00000000

Comment 1 by msrchandra@chromium.org, Jun 3 2016

Cc: msrchandra@chromium.org
Labels: OS-Linux
Owner: jsb...@chromium.org
Status: Assigned (was: Unconfirmed)
Providing the Stack Trace for the Crash Id -- f0fd965a00000000

Stack Trace ::
===============
Thread 11 CRASHED [SIGABRT @ 0x0000b69100004162 ] MAGIC SIGNATURE THREAD
0x00007f8936ab9c37	(libc-2.19.so + 0x00036c37 )	
0x00007f8936abd027	(libc-2.19.so + 0x0003a027 )	
0x00007f8936b6e738	(libc-2.19.so + 0x000eb738 )	
0x00007f8936afbf02	(libc-2.19.so + 0x00078f02 )	
0x00007f8936afc69e	(libc-2.19.so + 0x0007969e )	
0x00007f8936af1d9c	(libc-2.19.so + 0x0006ed9c )	
0x000055b55d0440a7	(chrome -./out/Release/../../base/logging.cc:735 )	logging::LogMessage::~LogMessage
0x000055b55d1a8925	(chrome -./out/Release/../../third_party/leveldatabase/src/db/skiplist.h:185 )	leveldb::SkipList<const char *, leveldb::MemTable::KeyComparator>::Insert
0x00007f892f3c3b80	(Databases.db + 0x00001b80 )	
0x000055b55d065524	(chrome -./out/Release/../../base/strings/string_number_conversions.cc:375 )	base::DoubleToString
0x000055b55d1a87b8	(chrome -./out/Release/../../third_party/leveldatabase/src/db/memtable.cc:105 )	leveldb::MemTable::Add
0x00007f89370e69b7	(libstdc++.so.6.0.19 + 0x000889b7 )	
0x00007f89370fb44f	(libstdc++.so.6.0.19 + 0x0009d44f )	
0x00007f89370fb44f	(libstdc++.so.6.0.19 + 0x0009d44f )	
0x00007f89370e6da9	(libstdc++.so.6.0.19 + 0x00088da9 )	
0x000055b5593e62fc	(chrome -./out/Release/../../third_party/tcmalloc/chromium/src/thread_cache.h:201 )	do_free_with_callback
0x000055b55d8a0ae1	(chrome -./out/Release/../../third_party/tcmalloc/chromium/src/tcmalloc.cc:1045 )	tc_malloc
0x000055b5593cfd79	(chrome -./out/Release/../../base/allocator/allocator_shim.cc:150 )	ShimCppNew
0x00007f8937118248	(libstdc++.so.6.0.19 + 0x000ba248 )	
0x00007f89371197ed	(libstdc++.so.6.0.19 + 0x000bb7ed )	
0x00007f89370f6f2c	(libstdc++.so.6.0.19 + 0x00098f2c )	
0x000055b55d043e21	(chrome -./out/Release/../../build/linux/debian_wheezy_amd64-sysroot/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/bits/basic_string.h:244 )	logging::LogMessage::Init
0x00007f89370fb44f	(libstdc++.so.6.0.19 + 0x0009d44f )	
0x00007f89370f2c04	(libstdc++.so.6.0.19 + 0x00094c04 )	
0x000055b55da44109	(chrome + 0x055ca109 )	_fini
0x000055b55da43ce0	(chrome + 0x055c9ce0 )	_fini
0x000055b55dae1f8b	(chrome + 0x05667f8b )	_fini
0x000055b55be38a6f	(chrome -./out/Release/../../dbus/bus.cc:1202 )	dbus::Bus::OnConnectionDisconnectedFilter
0x00007f8900000002	(pulse-shm-2881323837 + 0x00b83002 )	
0x00007f8900000007	(pulse-shm-2881323837 + 0x00b83007 )	
0x00007f893946012f	(libdbus-1.so.3.7.6 + 0x0002212f )	
0x000055b55da43cd5	(chrome + 0x055c9cd5 )	_fini
0x00007f893944c9d5	(libdbus-1.so.3.7.6 + 0x0000e9d5 )	
0x00007f8939463efd	(libdbus-1.so.3.7.6 + 0x00025efd )	
0x00007f8939449128	(libdbus-1.so.3.7.6 + 0x0000b128 )	
0x000055b55db4f536	(chrome + 0x056d5536 )	_fini
0x000055b55be39648	(chrome -./out/Release/../../dbus/bus.cc:828 )	dbus::Bus::ProcessAllIncomingDataIfAny
0x000055b55d032bdb	(chrome -./out/Release/../../base/callback.h:397 )	base::debug::TaskAnnotator::RunTask
0x000055b55da440c0	(chrome + 0x055ca0c0 )	_fini
0x000055b55da43cd5	(chrome + 0x055c9cd5 )	_fini
0x000055b55be3b5c8	(chrome -./out/Release/../../dbus/bus.cc:1106 )	dbus::Bus::OnDispatchStatusChanged
0x000055b55be3976f	(chrome + 0x039bf76f )	
0x00007f890014c6cf	(pulse-shm-2881323837 + 0x00ccf6cf )	
0x000055b55be3b5c8	(chrome -./out/Release/../../dbus/bus.cc:1106 )	dbus::Bus::OnDispatchStatusChanged
0x000055b55da440c0	(chrome + 0x055ca0c0 )	_fini
0x000055b55da43cd5	(chrome + 0x055c9cd5 )	_fini
0x000055b55be3b5c8	(chrome -./out/Release/../../dbus/bus.cc:1106 )	dbus::Bus::OnDispatchStatusChanged
0x00007f88ffffffff	(pulse-shm-2881323837 + 0x00b82fff )	
0x000055b55da43cd5	(chrome + 0x055c9cd5 )	_fini
0x000055b55d0480b4	(chrome -./out/Release/../../base/message_loop/message_loop.cc:479 )	base::MessageLoop::RunTask
0x00007f8939462389	(libdbus-1.so.3.7.6 + 0x00024389 )	
0x000055b55d04a44e	(chrome -./out/Release/../../base/message_loop/message_pump_libevent.cc:98 )	base::MessagePumpLibevent::OnLibeventNotification
0x000055b55d04868b	(chrome -./out/Release/../../base/message_loop/message_loop.cc:625 )	base::MessageLoop::DoDelayedWork
0x000055b55912003f	(chrome + 0x00ca603f )	
0x000055b55d8aff3b	(chrome + 0x05435f3b )	_fini
0x000055b55d0483d7	(chrome -./out/Release/../../base/message_loop/message_loop.cc:488 )	base::MessageLoop::DeferOrRunPendingTask
0x000055b55d04858a	(chrome -./out/Release/../../base/message_loop/message_loop.cc:600 )	base::MessageLoop::DoWork
0x000055b558fc310f	(chrome + 0x00b4910f )	
0x000055b55da440c0	(chrome + 0x055ca0c0 )	_fini
0x000055b55da43cd5	(chrome + 0x055c9cd5 )	_fini
0x000055b55be3b5c8	(chrome -./out/Release/../../dbus/bus.cc:1106 )	dbus::Bus::OnDispatchStatusChanged
0x000055b55d04a718	(chrome -./out/Release/../../base/message_loop/message_pump_libevent.cc:230 )	base::MessagePumpLibevent::Run
0x000055b55d0611ef	(chrome -./out/Release/../../base/run_loop.cc:35 )	base::RunLoop::Run
0x00007f89000003c4	(pulse-shm-2881323837 + 0x00b833c4 )	
0x000055b55d0478a9	(chrome -./out/Release/../../base/message_loop/message_loop.cc:295 )	base::MessageLoop::Run
0x000055b55a50c62d	(chrome -./out/Release/../../content/browser/browser_thread_impl.cc:188 )	content::BrowserThreadImpl::FileThreadRun
0x000055b55a50c741	(chrome -./out/Release/../../content/browser/browser_thread_impl.cc:243 )	content::BrowserThreadImpl::Run
0x000055b55d07e857	(chrome -./out/Release/../../base/threading/thread.cc:254 )	base::Thread::ThreadMain
0x000055b55d07b4a2	(chrome -./out/Release/../../base/threading/platform_thread_posix.cc:70 )	ThreadFunc
0x00007f8939991183	(libpthread-2.19.so + 0x00008183 )	
0x00007f8936b7d37c	(libc-2.19.so + 0x000fa37c )

The Stack Trace looks similar to that of Bug Id: 550323.
@jsbell -- Could you please look into the issue and update, pardon me if it has nothing to do with your changes.
Thank You.
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 3 2016

Labels: Hotlist-Google

Comment 3 by jsb...@chromium.org, Jun 3 2016

Cc: derat@chromium.org jsb...@chromium.org
Owner: hashimoto@chromium.org
This looks similar to issue 504113 - crash after dbus::Bus::OnConnectionDisconnectedFilter - 
Stack after that looks bogus - logging::LogMessage::Init shouldn't be calling into leveldb via the allocator.

Per derat@ "dbus-daemon isn't supposed to be restarted, so it also seems okay to just WontFix this. You can't temporarily disable the systemwide IPC bus without expecting random things to break"

Sounds like there's a repro here, though.

Comment 4 by derat@chromium.org, Jun 3 2016 

Is this crash repeatable? Is dbus-daemon in fact crashing?

Comment 5 by derat@chromium.org, Jun 3 2016

Labels: Needs-Feedback

Comment 6 by elil@google.com, Jun 6 2016 

I get this at least once a day, although often Chrome doesn't generate a crash report.  Please see crash report here for today's crash: 

Crash ID 11c183da00000000 (Chrome)

Comment 7 by elil@google.com, Jun 6 2016 

And two omre ni very quick succession:

Crash ID 3baadcdc00000000 (Chrome)
Crash ID 699843da00000000 (Chrome)

Comment 8 by derat@chromium.org, Jun 6 2016

Labels: -Restrict-View-EditIssue
For 3baadcdc00000000 and 699843da00000000, this is at the bottom of the trace:

0x000055c3464b6443	(chrome -./out/Release/../../base/process/memory.cc:19 )	OnNoMemory

I could imagine the kernel OOM killer also killing off dbus-daemon and causing the other intentional aborts that you're seeing.

How much RAM does your system have? Does "free" report that the system is near its limit? Do "dmesg" and/or /var/log/messages contain anything about the OOM killer after you see this?

Comment 9 by elil@google.com, Jun 6 2016 

8GB of RAM.

free says I'm using 85% of RAM with only Chrome running.  I've killed most
tabs, but don't see any drop in memory usage.

I have the following errors from /var/log/messages:

Jun  6 16:13:57 elil1.roam.corp.google.com cinnamon-session[3794]: WARNING:
Unable to load desktop file '/usr/bin/google-chrome-stable.desktop': No
such file or directory
Jun  6 16:13:57 elil1.roam.corp.google.com cinnamon-session[3794]: WARNING:
Unable to find desktop file 'google-chrome-stable.desktop': Valid key file
could not be found in search dirs
Jun  6 16:13:57 elil1.roam.corp.google.com cinnamon-session[3794]: WARNING:
Unable to find desktop file 'gnome-/usr/bin/google-chrome-stable.desktop':
Valid key file could not be found in search dirs

Jun  6 16:15:28 elil1.roam.corp.google.com pulseaudio[4064]: [pulseaudio]
module-alsa-card.c: Failed to find a working profile.
Jun  6 16:15:28 elil1.roam.corp.google.com pulseaudio[4064]: [pulseaudio]
module.c: Failed to load module "module-alsa-card" (argument:
"device_id="2" name="usb-046d_08ca_4821F9A1-02-U0x46d0x8ca"
card_name="alsa_card.usb-046d_08ca_4821F9A1-02-U0x46d0x8ca"
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
deferred_volume=yes use_ucm=yes
card_properties="module-udev-detect.discovered=1""): initialization failed.

And loads of these from dmesg:

[    5.054089] [drm:gen8_irq_handler [i915]] *ERROR* The master control
interrupt lied (SDE)!

Comment 10 by derat@chromium.org, Jun 6 2016 

What's in the logs around the time that Chrome crashed? Or is that it?

Comment 11 by derat@chromium.org, Jun 6 2016 

(Specifically, around the time of one of the D-Bus-related aborts?)

Comment 12 by elil@google.com, Jun 7 2016 

I didn't see anything that stood out, so here is the full output after
crash this morning.  See attached.

Lots of 'master control interrupt lied (SDE)' messages.

Comment 13 by primiano@chromium.org, Jul 19 2016 

are there any steps to reproduce this?

Comment 14 by rnimmagadda@chromium.org, Aug 23 2016 

@elil: Could you please provide an update on this issue as per #13.

Comment 15 by hdodda@chromium.org, Feb 7 2017

Cc: hdodda@chromium.org
Status: WontFix (was: Assigned)
We couldn't fetch the crash report for the given crash id . Hence , closing the issue.

Please feel free to raise a new issue in future if you face any issues with latest chrome channels.

Thanks!
►

Sign in to add a comment