Chrome 32 bit Froze - 64 bit chrome worked - While Creating XHR object
Reported by
alejandr...@gmail.com,
Jul 12 2016
|
|||||||||
Issue description
Chrome Version : Version 51.0.2704.106 m and 51.0.2704.103 m
URLs (if applicable) : Internal application
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: NA
Firefox 47and forward :works
IE 11: works
Chrome 64 bit 51.0.2704.106 works
Chrome 32 bit 51.0.2704.103 on Windows 7 Enterprise works
Chrome 32 bit 51.0.2704.106 on windows 7 pro fails
What steps will reproduce the problem?
(1) mini dumps when it fails on Chrome 32 bit 51 ... 103
(2) mini dumps when it breaks on Chrome 32 bit 51.. 106
(3) minidumps when it works on chrome 64 bit 51 106 on windows enterprise
(4) screenshow when we followed the code step by step the line marked as breakpoint is the last one we could run
What is the expected result?
The application will try to open a new URL in one of its Iframes,
What happens instead?
Chrome freezes, following code line by line we create an XHR object and then it freezes. keeping in Wait/kill dialogue indefinitely . CPU spikes to 25% RAM got to 800 MB
Please provide any additional information below. Attach a screenshot if
possible.
Screenshot attached.
,
Jul 13 2016
Hey, would you mind providing a sample file for the above issue ? Appreciate your help. Thank you!
,
Jul 13 2016
I've added several minidumps. Do you need something like the HTML / JS and try to replay it (I have replayable fiddler logs) ?
,
Jul 13 2016
last executed line
,
Jul 14 2016
Thank you for providing more feedback. Adding requester "ashejole@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
,
Jul 14 2016
Adding fiddler log that replicates the issue on the mentioned chrome versions, In order to replicate the problem 1. Import the farx in fiddler Auto responder 2. Enable Runes and start capturing with fiddler 3. Access URL on your chrome browser http://gems.daytonoh.ncr.com:8181/arsys/forms/gems/nsm3_gateway/GEMS+Web+Home/?cacheid=c7a45ca9 4. The form will be displayed, then click on "Search Incidents" button (middle left ) 5. A series of records will appear in bottom table 6. Click record number 4 on the table If you click the record and get to error [Fiddler] DNS Lookup for "gems.daytonoh.ncr.com" failed. System.Net.Sockets.SocketException No such host is known then the issue did not replicate. If you get to freeze / wait then the issue replicated.
,
Jul 20 2016
Hello, Is there any update on this issue ?
,
Aug 2 2016
Apologies for the late reply. Can you please try on the latest chrome version '52.0.2743.82' and request you let us know if the issue persists. I really appreciate your help. Thank you!
,
Aug 2 2016
,
Aug 2 2016
yes, the issue still happens on '52.0.2743.82' chrome 32 bit on Windows 7 pro.
,
Aug 3 2016
,
Aug 11 2016
Thank you for providing more feedback. Adding requester "eostroukhov@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
,
Aug 11 2016
,
Sep 27 2016
Hi, can you please supply us with a live demo or files that will reproduce this issue with instructions?
,
Dec 2 2016
Flagging as wont-fix as we cannot reproduce and has not had any feedback for many months. Feel free to comment here and I'll reopen it if needed. Thanks! |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by alejandr...@gmail.com
, Jul 12 2016