chrome crashes when Spotify is opened, then leaves an unkillable chrome.exe *32 process running
Reported by
aa260...@gmail.com,
Jun 21 2016
|
|||||||
Issue description
<b>Chrome Version : <Copy from: 'about:version'></b>
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
NOTE: this will not always reproduce it, however it happens on a daily basis to my machine
1. Open chrome immediately upon system start up
2. Close and re-open spotify (which has auto-launched)
3.
What is the expected result?
Chrome will become unresponsive and eventually you'll have to kill it. Then in task manager, a series of chrome.exe processes exist. Attempting to end process on the 186.424k one will not work, it won't die.
What happens instead of that?
Please provide any additional information below. Attach a screenshot if
possible.
,
Jun 22 2016
Could you please let us know the Chrome version used to reproduce it, and if any crash id to triage it further. Currently spotify is not available in India, requesting MTV team to take a look into this.
,
Jun 22 2016
Version is 51.0.2704.103 m. don't know how to get a crash id
,
Jun 23 2016
Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 23 2016
It crashed just now with this error message, just after I started Spotify. --------------------------------------------------------- Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: chrome.exe Application Version: 51.0.2704.103 Application Timestamp: 57610a1f Hang Signature: a95f Hang Type: 0 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Hang Signature 1: a95f944750a589f67f5110bbd217ba2b Additional Hang Signature 2: a2e4 Additional Hang Signature 3: a2e44cb1ed37f43b7a877a78bd79f5da Additional Hang Signature 4: a95f Additional Hang Signature 5: a95f944750a589f67f5110bbd217ba2b Additional Hang Signature 6: a2e4 Additional Hang Signature 7: a2e44cb1ed37f43b7a877a78bd79f5da Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
,
Jun 27 2016
Thank you for the feedback. Navigate to Chrome://crashes in the chrome browser and look for the latest crash Id and update the thread.
,
Jun 27 2016
It doesn't appear in the list of crashes. Likely because I had to close out of the window and "kill" the process because it stalled out
,
Jul 12 2016
This is still an open issue, which is causing me to migrate my browser use to Mozilla. If this won't get fixed, I'm gonna just end up switching entirely since Mozilla never crashes like this
,
Aug 25 2016
,
Aug 25 2016
We need more information to diagnose this bug. If you can't get a crash id, can you go to chrome://tracing and try to record a trace around the time that chrome becomes unresponsive? Thank you
,
Aug 25 2016
Also try disabling any extensions and plugins in chrome you have and see if the problem continues. If it goes away, try to narrow down which extension/plugin may be responsible by re-enabling them gradually.
,
Apr 7 2017
Closing since we can't repro and there hasn't been any update in a while. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 Deleted