Chrome crashed while debugging no crash id given why?
Reported by
mikhail....@gmail.com,
Sep 7 2016
|
||||||||
Issue description
,
Sep 9 2016
@mikhail.v.gavrilov -- Could you please provide steps to reproduce the issue. Navigate to chrome://settings and verify whether the option "Automatically send usage statistics and crash reports to Google" is checked or not. Thanks in Advance.
,
Sep 12 2016
mikhail, can you get copy the crash ID information from chrome://crashes/ ? you can also reply in Russian if you like. The Devtools team are native speakers. :)
,
Sep 15 2016
As you can see I have enabled "Automatically send usage statistics and crash reports to Google" option (chrome1.PNG) But no more crashes added to chrome://crashes/ since 27 July. Described here crash occured 7 Sep.
,
Sep 23 2016
Thank you for providing more feedback. Adding requester "msrchandra@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
,
Sep 30 2016
,
Oct 10 2016
It's hard to tell what's going on without a repro or crash id. Looks like out-of-memory crash. Mikhail, if you can repro it, could you please open the Chrome Task Manager and check what's the tab memory size before the crash? Thank you.
,
Oct 10 2016
,
Oct 16 2016
Coredump here: https://dumps.sy24.ru/ccpp-2016-10-15-12:50:15-23998.tar.xz
,
Oct 24 2016
The crash id corresponds to out of memory crash: 0x000055cd6d790993 (chrome -./out/Release/../../third_party/WebKit/Source/bindings/core/v8/V8Initializer.cpp:108 ) blink::reportOOMErrorInMainThread 0x000055cd6d79095f (chrome + 0x03c4795f ) 0x000055cd6a8f11bb (chrome -./out/Release/../../v8/src/api.cc:375 ) v8::Utils::ReportOOMFailure 0x000055cd6f6c2cb2 (chrome + 0x05b79cb2 ) _fini 0x000055cd6a8f1168 (chrome -./out/Release/../../v8/src/api.cc:338 ) <name omitted> I don't think we can do anything here.
,
Oct 24 2016
I want show you two screen. At first screen [Screenshot from 2016-10-24 19-47-30.png] we see a lot of google chrome crashes, but at second screen [Screenshot from 2016-10-24 21-30-38.png] we see what half of virtual memory is free. Paging partition having size 59.6G, but it stop growing at size 29.7Gb. And this is most misunderstanding here. I am understand if out of memory crash occured when page partition no left free space, but it occurring again and again when page partition filled at half space. This is strange, can you investigate this? May be this is unknown kernel bug.
,
Oct 25 2016
@dgozman Are you hear me? |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by rnimmagadda@chromium.org
, Sep 8 2016