OOM intervention triggered on loading causes DCHECK in document loader |
||
Issue descriptionError message: FATAL:document_loader.cc(751)] Check failed: !response_.IsNull() I am unable to get the stack trace for some reason. Steps to repro: Enable OOM intervention pausing on debug build on low end device. Load http://phukiengiabuon.vn/ The page stops loading as expected. But hits a dcheck later. Assigning to yuzu@ for now.
,
May 21 2018
I noticed the same issue. This bug might be responsible for the higher RendererCrash rate in the intervention experiment.
,
May 22 2018
It might be possible that the relevant task is getting posted to the default task queue which we can't pause. It would be very useful to see a stack trace and a location from which the task in question is posted.
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
||
►
Sign in to add a comment |
||
Comment 1 by ssid@chromium.org
, May 18 2018