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

Issue 698115 link

Starred by 1 user
Status: WontFix
Owner:
█ uekawa@chromium.org
Last visit > 30 days ago
Closed: Dec 2017
Cc:
ka...@chromium.org
sontis@chromium.org
steve...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

suspend/resume slow, crash

Project Member Reported by uekawa@chromium.org, Mar 3 2017 
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: 57.0.2987.75
Operating System: Linux 3.14.0

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. log in to corp (multi-profile makes it happen more often?)
2. suspend
3. resume and log in

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

Comment 1 by uekawa@chromium.org, Mar 3 2017 

0xab6f5b36	(libc-2.23.so + 0x00016b36 )	__libc_do_syscall
0xab704cd3	(libc-2.23.so -raise.c:54 )	raise
0xab705c35	(libc-2.23.so -abort.c:89 )	abort
0xab831747	(libstdc++.so.6.0.20 -vterminate.cc:95 )	__gnu_cxx::__verbose_terminate_handler()
0xab83010d	(libstdc++.so.6.0.20 -eh_terminate.cc:47 )	__cxxabiv1::__terminate(void (*)())
0xab83016b	(libstdc++.so.6.0.20 -eh_terminate.cc:57 )	std::terminate()
0xab8303c7	(libstdc++.so.6.0.20 -eh_throw.cc:87 )	__cxxabiv1::__cxa_throw
0xab98f6cb	(libdbus-c++-1.so.0.0.0 -connection.cpp:373 )	DBus::Connection::send_blocking(DBus::Message&, int)
0xab98b579	(libdbus-c++-1.so.0.0.0 -object.cpp:445 )	virtual thunk to DBus::ObjectProxy::_invoke_method(DBus::CallMessage&)
0xab987c7d	(libdbus-c++-1.so.0.0.0 -interface.cpp:181 )	DBus::InterfaceProxy::invoke_method(DBus::CallMessage const&)
0x2b661da3	(network_status -org.chromium.flimflam.Manager.h:33 )	org::chromium::flimflam::Manager_proxy::GetProperties()
0x2b6614fd	(network_status -network_status.cc:124 )	GetDevices(DBus::Connection*, ManagerProxy*)
0x2b661771	(network_status -network_status.cc:147 )	main
0xab6f587d	(libc-2.23.so -libc-start.c:289 )	__libc_start_main
0x2b660aa7	(network_status + 0x00003aa7 )	_start
0x2b6667eb	(network_status -elf-init.c:87 )	__libc_csu_init
0xab9c3e43	(ld-2.23.so + 0x0000be43 )	_dl_sort_fini
0x2b660a73	(network_status + 0x00003a73 )	_init

Comment 2 by ajha@chromium.org, Mar 9 2017

Labels: OS-Chrome

Comment 3 by tgillella@chromium.org, Nov 3 2017

Cc: ka...@chromium.org sontis@chromium.org
Components: Platform
Labels: M-63

Comment 4 by sontis@chromium.org, Nov 3 2017

Components: -Platform OS>Kernel>Power

Comment 5 by derat@chromium.org, Nov 3 2017

Cc: steve...@chromium.org
Components: OS>Systems>Network
Labels: -Restrict-View-EditIssue -User-Submitted -M-63 Needs-Feedback
The crash report seems to be gone now. :-(

Are you still seeing this? If so, can you file a feedback report after triggering it?

Comment 6 by tbroch@chromium.org, Dec 1 2017

Owner: uekawa@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 7 by uekawa@google.com, Dec 14 2017

Status: WontFix (was: Assigned)
can't reproduce this specific thing anymore
►

Sign in to add a comment