Unable to upload Crashes with WiFi networks |
|||
Issue descriptionChrome Version: 64.0.3282.24 OS: 10176.14.0 & 10176.13.0 What steps will reproduce the problem? (1) Trigger any browser or kernel crash (about:crash, about:inducebrowsercrashforrealz or alt + f10 + XXX etc) (2) Open about:crashes and click on '"Start Uploading Crashes" link to upload the crash report What is the expected result? All crashes are uploaded What happens instead? Crashes are not getting uploaded on any of the WiFi network available (tried with: Googleguest, Cros_AU-2.4GHz & Cros_AU-5GHz). Able to upload only when connected with Ethernet Please use labels and text to provide additional information. Logs attached. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Dec 14 2017
Tested on Eve, Caroline & Minnie and see the same issue.
,
Dec 14 2017
,
Dec 14 2017
looks like a networking problem and unrelated to crash. looks to me like crash_sender is WAI here. are you sure your WiFi is working correctly ? from /var/log/messages: 2017-12-14T22:26:10.730015+00:00 NOTICE crash_sender[7747]: Considering metadata /home/chronos/u-e7c123dadec14b8fffe1e416892ea43182971c5d/crash/chrome.20171214.142547.1988.meta. 2017-12-14T22:26:10.755527+00:00 NOTICE crash_sender[7762]: Current send rate: 1sends/24hrs 2017-12-14T22:26:10.761856+00:00 NOTICE crash_sender[7768]: Scheduled to send in 7s. 2017-12-14T22:26:17.864934+00:00 NOTICE crash_sender[7847]: Sending crash: 2017-12-14T22:26:17.865568+00:00 NOTICE crash_sender[7848]: Sending crash report on behalf of Chrome_ChromeOS 2017-12-14T22:26:17.866146+00:00 NOTICE crash_sender[7849]: Metadata: /home/chronos/u-e7c123dadec14b8fffe1e416892ea43182971c5d/crash/chrome.20171214.142547.1988.meta (minidump) 2017-12-14T22:26:17.866811+00:00 NOTICE crash_sender[7850]: Payload: /home/user/e7c123dadec14b8fffe1e416892ea43182971c5d/crash/chrome.20171214.142547.1988.dmp 2017-12-14T22:26:17.867405+00:00 NOTICE crash_sender[7851]: Version: 64.0.3282.24 2017-12-14T22:26:17.872252+00:00 NOTICE crash_sender[7852]: Boot mode: dev 2017-12-14T22:26:17.873426+00:00 NOTICE crash_sender[7853]: Exec name: chrome 2017-12-14T22:26:17.906212+00:00 INFO list_proxies[7854]: Resolving proxies for URL: https://clients2.google.com/cr/report 2017-12-14T22:26:17.907658+00:00 INFO list_proxies[7854]: Got proxies: direct:// 2017-12-14T22:26:18.355432+00:00 ERR shill[2070]: [ERROR:active_link_monitor.cc(222)] Link monitor has reached the failure threshold with 5 broadcast failures and 0 unicast failures. 2017-12-14T22:26:20.677818+00:00 ERR shill[2070]: [ERROR:dhcp_config.cc(285)] Timed out waiting for DHCP lease on wlan0 (after 30 seconds). 2017-12-14T22:26:24.716819+00:00 INFO avahi-daemon[2529]: Server startup complete. Host name is 503067eb70f023b588d4bffd5a32fa6e.local. Local service cookie is 4132743825. 2017-12-14T22:26:27.936811+00:00 NOTICE crash_sender[7863]: Crash sending failed with exit code 6: * Curl_ipv4_resolve_r failed for clients2.google.com#012* Couldn't resolve host 'clients2.google.com'#012* Closing connection 0#012curl: (6) Couldn't resolve host 'clients2.google.com' 2017-12-14T22:26:27.941555+00:00 NOTICE crash_sender[7865]: Problem sending /home/chronos/u-e7c123dadec14b8fffe1e416892ea43182971c5d/crash/chrome.20171214.142547.1988.meta, not removing.
,
Dec 14 2017
WiFi networks are not reliable since last couple hours.
,
Dec 14 2017
OK, so is this bug still valid ?
,
Dec 15 2017
Restarted the WiFi router and seems to be working fine now. Closing this bug as of now. |
|||
►
Sign in to add a comment |
|||
Comment 1 by pgangishetty@chromium.org
, Dec 14 2017