Chrome shows Aw snap message while visiting my website
Reported by
cjeff...@gmail.com,
Nov 16 2017
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue descriptionVersion: <Insert version or Git hash> OS: <Windows> Architecture: <ARM, x64, x86> What steps will reproduce the problem? 1.visit the http://trade.smcindiaonline.com/easytrade 2.keep the site in login state What is the expected output? The site should be working fine with constant login What do you see instead? Chrome shows Aw snap window Note: not able to find the issue as the developer console disconnects as the issue occurs.
,
Nov 17 2017
do you have a crash ID too?
,
Nov 17 2017
yup. This is a list of crash files generated as the issue occurred. was not able to upload the file due to some issue. Please kindly look into it.
,
Nov 20 2017
Tested the issue on windows 10 & Mac os 10.12.6 using chrome stable M62 #62.0.3202.94 and M64 #64.0.3273.0 and followed below steps: 1. Launched chrome and navigated to "http://trade.smcindiaonline.com/easytrade" and found that there is not option to register and the login page is not crashing. @Could you please try in afresh chrome profile without any extensions and flags enabled and if you can still see the issue , please provide us the chrome OS and version details and also the crash id (Refer screencast ending part). Thanks!
,
Nov 24 2017
Hi,
We have created tool for simulating the issue.
1. To simulate the issue please navigate to http://203.114.240.122/websockettest/
and input IP as 203.114.240.122 and port as 4509
2. After successful connection please send the following requests in the send message field
a)
63=FT3.0|64=206|65=85|66=11:18:59|4=0x01353C516AB78E2DBBA17789A9943F|1=1$7=2918|230=1
b)
63=FT3.0|64=159|65=117|66=13:16:02|4=0x01F98DD7830952A1D1CBA0781AF3DA|95=1|309=0|310=9999999999999|1=1|38=1|32=|36=10
3. Send the second request 3 times in a row after the first request.
The page shows Aw snap message after aprox 10 seconds.
Kindly look into it for simulation of the issue.
Thanks!
,
Nov 24 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 27 2017
Tested the issue on windows 10 & MAc os 10.12.6 using chrome M62 #62.0.3202.94 with the steps mentioned in comment #5 and not able to reproduce the issue. Attached screencast for reference. @ cjeffrin-- could you please check attached screencast and confirm us if we have missed any steps in reproducing the issue and also help us with the crash id and report id from the chrome://crashes and screencast of the issue for better traiging. Thanks!
,
Dec 1 2017
The steps performed we're right. Please kindly try these setting in the environment. URL : https://trade.smcindiaonline.com/easytrade/soctesttool/ IP: trade.smcindiaonline.com Port : 4509 Please click the wss mode click the second radio button for that. thanks
,
Dec 1 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 5 2017
Tested the issue on windows 10 and Mac OS 10.12.6 using chrome M62 #62.0.3202.94 and M65 #65.0.3285.0 and issue is not reproduced with the steps mentioned in comment #8 & #10. Attached screencast for reference. @ cjeffrin-- Please provide us the uploaded crash id from chrome://crashes instead of the local id or dump file for better traiging process. Also please provide us the chrome Os and version details in which you are facing this issue. Thanks!
,
Dec 5 2017
Hi, This is the crash ID 1. 718f520e-279a-459b-82bf-78d295f503dd 2. faa1d49b-d770-4861-8c27-a70e19c67a0b 3. f3f4cece-7587-41a3-a6fa-75b0bf4fe641 Kindly look into the attachement for the version details i guess the websocket response is trade market related so i think chrome crashes after market hours. Please try after 5 or 6 pm IST if issue is not simulating. this is just my guess but the last request's response i send is not shown on the chromes network dev tools or the chrome crashes before its received. Thanks
,
Dec 5 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 7 2017
Hi, This is the Id generated from internal workspace with the same I have attached the version details of the machine as well 1) Uploaded Crash Report ID 2bbbc400a58bc0c0 (Local Crash ID: a12a0647-cd6a-4922-a12c-1424b7f0763d) Crash report captured on Friday, November 17, 2017 at 11:39:26 AM, uploaded on Friday, November 17, 2017 at 4:31:07 PM 2) Uploaded Crash Report ID ed274d9cc91f760a (Local Crash ID: be34cc47-9909-48fa-935a-b057b08f1880) Crash report captured on Friday, November 17, 2017 at 11:29:12 AM, uploaded on Friday, November 17, 2017 at 4:31:06 PM 3) Uploaded Crash Report ID ef3bd2ab33e70477 (Local Crash ID: 9d0e0465-efc9-48b3-a350-a2b05ff33812) Crash report captured on Friday, November 17, 2017 at 11:26:58 AM, uploaded on Friday, November 17, 2017 at 4:31:06 PM
,
Dec 7 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 8 2017
cjeffrin@ Thanks for the issue. Tested this issue on Windows 7 and Mac OS 10.12.6 on the latest Canary 65.0.3287.0 and Stable 63.0.3239.84 and unable to reproduce this issue. Cannot observe any crash on following the steps mentioned in comment #10. From the given Crash ID's 2bbbc400a58bc0c0, ed274d9cc91f760a, ef3bd2ab33e70477 these crashes happened due to Out of memory. Below is the stack trace for the same. Thread 12 (id: 8820) CRASHED [EXCEPTION_BREAKPOINT @ 0x00007ffed05a4894 ] MAGIC SIGNATURE THREAD Stack Quality85%Show frame trust levels 0x00007ffed05a4894 (chrome_child.dll -debugger_win.cc:21 ) base::debug::BreakDebugger() 0x00007ffecfedbb65 (chrome_child.dll -logging.cc:784 ) logging::LogMessage::~LogMessage() 0x00007ffed17f7795 (chrome_child.dll -v8initializer.cpp:528 ) blink::ReportFatalErrorInWorker 0x00007ffed01d3d3b (chrome_child.dll -api.cc:417 ) v8::Utils::ReportOOMFailure(char const *,bool) 0x00007ffecfcf2e73 (chrome_child.dll -api.cc:386 ) v8::internal::V8::FatalProcessOutOfMemory(char const *,bool) 0x00007ffecfd6c08d (chrome_child.dll -heap.cc:4017 ) v8::internal::Heap::AllocateRawFixedArray(int,v8::internal::PretenureFlag) 0x00007ffecf62b649 (chrome_child.dll -heap-inl.h:221 ) v8::internal::Heap::AllocateFixedArray(int,v8::internal::PretenureFlag) 0x00007ffecf5f0df0 (chrome_child.dll -factory.cc:190 ) v8::internal::Factory::NewUninitializedFixedArray(int) 0x00007ffecfb39839 (chrome_child.dll -elements.cc:845 ) v8::internal::`anonymous namespace'::ElementsAccessorBase<v8::internal::`anonymous namespace'::FastPackedSmiElementsAccessor,v8::internal::A0xb4ac5a27::ElementsKindTraits<0> >::ConvertElementsWithCapacity 0x00007ffed02cab88 (chrome_child.dll -elements.cc:955 ) v8::internal::`anonymous namespace'::ElementsAccessorBase<v8::internal::`anonymous namespace'::FastPackedSmiElementsAccessor,v8::internal::A0xb4ac5a27::ElementsKindTraits<0> >::GrowCapacity 0x00007ffed037a1d4 (chrome_child.dll -runtime-array.cc:521 ) v8::internal::Runtime_GrowArrayElements(int,v8::internal::Object * *,v8::internal::Isolate *) 0x0000014f398847a0 0x00007ffed037a0e7 (chrome_child.dll + 0x00f1a0e7 ) Request you to please retry the issue by updating Chrome to the latest version, clearing all the cookies and cache data and update the thread with the observations. Thanks...
,
Dec 16 2017
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 19 2017
This is OOM. Can you pinpoint this to a Chrome version? Is this suddenly happening after a Chrome update?
,
Dec 19 2017
This is not a traditional OOM. The heap is really small (few MBs). What happens is that we run into the limit (128M) of allocating a new FixedArray. Camillo, can you have a look? Maybe we stay in fast mode for flat arrays too long.
,
Dec 19 2017
I just retried again on my windows machine with Chrome 63.0.3239.84 and I'm unable to reproduce the issue. cjeffrin@ would it be possible to create a standalone html page to reproduce the bug? The code-paths leading to the OOM are most probably coming from Array.prototype.push which greatly limits the possible origins: - channel.js: DeCompressData, HandleNormalData, OnSocketDataReceive - zlib.js: zip_inflate, zip_deflate By commenting out one function at a time you should be able to quickly determine which one causes the OOM. Once you have that you can intercept the socket message and create a standalone test case that simply replays the messages predictably.
,
Dec 19 2017
Additional advice: I see you have several extensions installed, please disable them completely for an accurate reproduction of the bug.
,
Jan 8 2018
Without a repro this is non-actionable, feel free to reopen. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comment 1 by hablich@chromium.org
, Nov 17 2017