Inspecting |event.source| in DevTools crashes renderer when the source is out of process. |
||||||
Issue description
Version: 57.0.2926.1 (Official Build) canary SyzyASan (32-bit)
OS: All
What steps will reproduce the problem?
(1) Create a page with an out of process <iframe>.
(2) Add a message handler to the page:
window.addEventListener('message', function(e) {
console.log(JSON.stringify(e.data));
};
(3) Open DevTools for the page and put a break point inside the message handler.
(4) Open another DevTools window inside <iframe> and type:
window.parent.postMessage({}, '*');
Alternatively, find another way that the <iframe> will post message to its parent.
(5) When the breakpoint hits, type e.source in console.
e.source| inside console.
What is the expected result?
The source should be shown as some type of Window object.
What happens instead?
The renderer crashes.
Typing 'e' alone is fine and it shows it has a window attribute.
,
Nov 21 2016
I was able to repro this using Windows Canary and http://csreis.github.io/tests/post-message.html : 0. Enable --site-per-process 1. Load http://csreis.github.io/tests/post-message.html 2. Click "load cross-site iframe" 3. Right click and inspect the iframe. 4. On the "Sources" tab in devtools, open the 'post-message-subframe' document, and set a breakpoint on line 21, [var msg = "bar";]. 5. In the original page, click the "postMessage to subframe" button. 6. In the debugger window, the breakpoint should be hit. 7. Type |e.source| and hit enter. 8. Receive crash.
,
Nov 21 2016
I noted that the crash happens for out of process sources. So it does not only affect OOPIFs.
In fact, I tried it on 53.0.2773.0 (Developer Build) (64-bit) with the following steps:
1) Open a page with embedded PDF (<embed src="PDF_URL"></embed>).
2) Add message handler to the page like above.
3) In DevTools for the page type: document.querySelector('embed').postMessage({}).
4) There will be a message from the PDF (type: 'documentLoaded').
5) Type e.source in console.
,
Nov 21 2016
Assigning the bug to dgozman@ following nasko@'s suggestion.
,
Nov 22 2016
,
Jan 4 2017
,
Oct 16 2017
,
Dec 12 2017
Looks like it is not crashing any more. Please reopen this one if it is still an issue. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ekaramad@chromium.org
, Nov 21 2016