Chrome kept restarting itself (not crash) |
|||
Issue descriptionGoogle Chrome 61.0.3154.0 (Official Build) unknown (64-bit) Platform 9737.0.0 (Official Build) dev-channel eve test powerd.out --- [0712/173007:FATAL:set_wifi_transmit_power.cc(144)] No wireless driver found /usr/lib64/libbase-core-395517.so(base::debug::StackTrace::StackTrace()+0x13) [0x7dfe0dce1e73] Aborted --- IIRC chrome restarts itself when some service (or dbus?) is dead. I thought powerd should be restarted by session manager, but I'm not sure. -> derat@ who is powerd owner.
,
Jul 12 2017
Nope, that's not correct. powerd isn't crashing here; set_wifi_transmit_power is. set_wifi_transmit_power does a LOG(FATAL) if it doesn't find a wireless interface named "mlan0" or "wlan0": [0712/173007:FATAL:set_wifi_transmit_power.cc(144)] No wireless driver found This is harmless, as far as I'm aware, but it produces a crash report and can be confusing. I filed a bug at http://b/63630261 about cleaning this up. Chrome doesn't restart itself at all. Chrome aborts and gets restarted by session_manager if its connection to dbus-daemon goes away. session_manager doesn't have anything to do with powerd either. So I don't know what this bug is tracking. If Chrome is restarting unexpectedly, please paste the relevant Chrome and session_manager logs. session_manager's log messages end up in /var/log/messages.
,
Jul 12 2017
By restart itself, I meant aborting and letting session manager start it. (I think chrome://restart does the same too) If it's not crsahing, then where this "Aborted" message came from? When this was happening, chrome was complaining that it can't connect to powerd. It was in guest mode, but unfortunately, I can't repro this state now though. That's being said, I just realized that guest mode won't show the restore UI, so this may be same as crbug.com/740820 .
,
Jul 12 2017
powerd.out contains stderr and stdout from the powerd process. This includes output from other processes that powerd runs, like set_wifi_transmit_power. That "Aborted" message is from set_wifi_transmit_power, not powerd, as I understand it. If you check /var/log/messages, it should also tell you when processes crash, I believe. Can you paste the errors from Chrome?
,
Jul 13 2017
Believe this is the fix (revert) for the issue based on conversation w/ Oshima. https://chromium-review.googlesource.com/#/c/566518/ Oshima can you confirm & close if thats the case as patch has landed & should be in chrome: 61.0.3155.0 https://chromium.googlesource.com/chromium/src/+log/61.0.3154.0..61.0.3155.0?pretty=fuller&n=10000
,
Jul 13 2017
Yeah, let's close this for now. Please let me know if you see similar restarts with PowerMananager related message in chrome log. |
|||
►
Sign in to add a comment |
|||
Comment 1 by tbroch@google.com
, Jul 12 2017