Issue metadata
Sign in to add a comment
|
chrome crashes when memory-infra is enabled in chrome://tracing |
||||||||||||||||||||||
Issue descriptionGoogle Chrome 52.0.2727.0 (Official Build) dev (64-bit) Revision 99526c41079e7de62a26a9c2cb9619a78f4df60a-refs/heads/master@{#392210} Platform 8302.0.0 (Official Build) dev-channel stumpy Repro step: 1) chrome://tracing 2) enable memory-infra 3) start recording It always print this line when crashed: [30683:30699:0520/110308:ERROR:memory_dump_manager.cc(483)] Disabling MemoryDumpProvider "V8Isolate". Failed to post task on the task runner provided. I don't know when this was regressed, nor this happens on other platforms. https://codereview.chromium.org/1618703004 may be culprit. ssid@ can you look into this?
,
May 20 2016
I also see that browser tests are passing on ChromeOS bots (MemoryTracingTest). Is there a bot that is failing or failing locally?
,
May 20 2016
,
May 20 2016
I couldn't reproduce locally on linux desktop which may behave differently. I'll test it on device.
,
May 20 2016
Google Chrome 52.0.2739.0 (Official Build) unknown (64-bit) Revision e63177a3d418d078a8777d83f817c11e30831d7b-refs/heads/master@{#393996} Platform 8352.0.0 (Official Build) dev-channel link test Chrome didn't crash but tracing page got frozen when I pressed "Stop" with the message "Recording... Buffer usage: x%" I'll test ToT.
,
May 20 2016
Looks like the freeze was crbug.com/613122 , and crash is gone on recent build, so I'll close this for now. I'll reopen if this happens again. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ssid@chromium.org
, May 20 2016