NaCl process crashing every five minutes on Windows 10 Creators Update
Reported by
gra...@kennery.com,
Apr 20 2017
|
||||
Issue descriptionChrome Version : 58.0.3029.81 (64-bit) URLs (if applicable) : https://chrome.google.com/webstore/detail/videostream-for-google-ch/cnciopoikihiagdjbjpnocolokfelagl What steps will reproduce the problem? (1) Load up NaCl module (2) Wait five minutes (3) What is the expected result? NaCl process not crashing What happens instead? NaCl process crashes Please provide any additional information below. Attach a screenshot if possible. This is quite a strange one, a bunch of our users (Videostream) are experiencing our NaCl process crashing on what seems to be a pretty standard interval of five minutes. Our process can even be sitting idle, waiting for commands from our Javascript background page, and it'll crash *every* five minutes. This is happening to users who upgrade to Windows 10 Creators Update and they didn't have any issues prior to this. We haven't been able to reproduce the issue on our own systems but we were able to have remote desktop sessions with some users to gather this information. Let me know if there is other information I can grab from these users to help figure out the cause of this. From the Windows System information, I was able to get the following Windows Error Reporting entries: 19/4/2017 21:28 Windows Error Reporting Fault bucket 120744276703, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: chrome.exe P2: 58.0.3029.81 P3: 58f6b153 P4: ntdll.dll P5: 10.0.15063.0 P6: b79b6ddb P7: c0000008 P8: 00000000000a918a P9: P10: Attached files: \\?\C:\Users\KawëAarknoff\AppData\Local\Temp\WER8151.tmp.WERDataCollectionStatus.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8162.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8160.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8180.tmp.txt \\?\C:\Users\KawëAarknoff\AppData\Local\Temp\WER8961.tmp.appcompat.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_chrome.exe_21c53f9c585e9a8d5d8b55e696c7b4d2abd878_ce17ebb6_231b898d Analysis symbol: Rechecking for solution: 0 Report Id: 6efaa21a-74f7-4ab6-8939-587203940b17 Report Status: 2147618824 Hashed bucket: 2452807e096ec633c07fa1bb059e3e87 19/4/2017 21:33 Application Error Faulting application name: chrome.exe, version: 58.0.3029.81, time stamp: 0x58f6b153 Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xb79b6ddb Exception code: 0xc0000008 Fault offset: 0x00000000000a918a Faulting process id: 0x1ff8 Faulting application start time: 0x01d2b953ef348b66 Faulting application path: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: ba9c49d2-3ce6-4048-a551-73dea57f4ddf Faulting package full name: Faulting package-relative application ID:
,
Apr 21 2017
We were just able to reproduce the issue in-house with the most recent: Windows 10 Creators Edition Chrome Stable Channel *Avast Anti-virus*
,
Apr 24 2017
Unable to reproduce this issue on Windows 10 with chrome version #58.0.3029.821. Loaded the provided extension in comment #0 in chrome browser and waited for 10-30 min but i didn't observe any crash. Machine Details: =============== Windows 10 version 1703 OS Build 15063.138 graham@ could you re-try the same scenario on clean profile with no apps/extensions and let us know your observations.
,
Apr 24 2017
kkaluri@ We were able to reproduce the crash with either Avast or AVG installed on the machine. Both of these anti-viruses crash NaCl exactly every 5 minutes.
,
May 24 2017
If you are still seeing the crash , please provide the server id from chrome://crashes.
,
May 31 2017
If for some reason chrome://crashes isn't showing any data then you can configure local recording of Windows Error Reporting Crash Dumps, as explained here: https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396 Since it seems likely that this is an Avast/AVG bug it would also be helpful to share the crash dumps with them. Chrome's symbol server should make it so that they can easily explore our code in the crash dumps - more easily than we can explore theirs.
,
Jul 31 2017
Removing from Bisect bucket since TE was not able to repro.
,
May 23 2018
As there is no action on this issue for long time closing this issue. Request you to update your Chrome to latest #66.0.3359.181 and verify. Feel free to file a new issue if the issue is still reproduced at your end. Thanks! |
||||
►
Sign in to add a comment |
||||
Comment 1 by ligim...@chromium.org
, Apr 20 2017