New issue
Advanced search Search tips

Issue 838902 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

-FlooredIntPoint(FrameOwnerContentsLocation()) ownerLayoutObject was nullptr.

Reported by rmill5...@gmail.com, May 2 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
Intermittent crash but numerous times a day for many of our users using chrome

What is the expected behavior?
No crashing

What went wrong?
A radwindow closes, the tab refreshes and returns a "Page cannot be displayed" message.  Numerous users all using chrome.  This did not happen before release 66.  All dump files return the message of "The thread tried to read orr write to a virtual address for which it does not have the appropriate access".  Debugging the dmp files shows "ownerLayoutObject was nullptr".  These are all at line 1314 of CompositedLayerMapping.cpp file at     graphics_layer_parent_location =
        -FlooredIntPoint(FrameOwnerContentsLocation());

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? Yes Chrome 65

Chrome version: 66.0.3359.139  Channel: stable
OS Version: 10.0
Flash Version:
 
9e5ccc1c-3a18-459f-af9f-fcf5cdf80693.dmp
754 KB Download
411f5613-d987-48f9-b441-c1ca165e38bf.dmp
886 KB Download
Labels: TE-NeedsTraige-help
Seems it is out of scope from TE end, adding TE-NeedsTraige-help label to move this out of our triaging bucket.

Could someone from dev team please take a look into this issue.
Thanks..!
Components: Blink>Paint
Cc: chrishtr@chromium.org
Components: -Blink>Paint Blink>Compositing
Labels: -Pri-2 Pri-1
This looks a lot like an OOPIF-related bug. Any idea on who should look at it?
Cc: kenrb@chromium.org
Hi,

We need crash ids (from navigating to about:crashes) or particular URLs that
seem to trigger the issue.

Comment 6 by kenrb@chromium.org, Jun 3 2018

The report is on Chrome 66, so this seems very likely to be fixed in r548507, which would be in Chrome 67.
Status: WontFix (was: Unconfirmed)
Marking as fixed. We can reopen if it turns out it starts to happen again.

Sign in to add a comment