Devtools protocol hangs on navigation in angular app
Reported by
math...@madumbo.com,
Feb 8 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Steps to reproduce the problem: 1. Use devtools protocol with chrome headless to navigate to index.html 2. Call Page.navigate to index.html#!/next What is the expected behavior? The browser should open the second link and the Page.navigate promise should resolve. What went wrong? The promise never resolves. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 64.0.3282.140 (Build officiel) (64 bits) Channel: stable OS Version: Manjaro 4.14.16-1 Flash Version: 28.0.0.161 ~/.config/google-chrome/PepperFlash/28.0.0.161/libpepflashplayer.so If we trigger another Page.navigate the first one gets withdrawn with an Err:Net_aborted. (add "void Page.navigate(...)" before the second await Page.navigate)
,
Feb 8 2018
Update: in my code, the second 'loadEventFired' hangs because the page has not been reloaded (because it is handled by angular) so we can omit/ignore it. With v64 the code hangs on the second Page.navigate, with v65, this whole test works fine. What prevents it to work with v64?
,
Feb 8 2018
,
Feb 9 2018
,
Feb 9 2018
Update #2: I put together a script triggering a freeze from the Debugger. In this script, the debugger is paused but does not resume. This bug is also reproducible with the devtool GUI.
,
Feb 9 2018
Update #3: It seems that the first bug I talk about (the Page.navigate hanging) has been fixed in this commit https://bugs.chromium.org/p/chromium/issues/detail?id=768961#c1 However, the second bug about the Debugger still remains.
,
Feb 12 2018
,
Feb 14 2018
awesome. I filed the debugger issue separtely as issue 812091 also investigated it a bit and it looks really interesting. thanks for reporting!
,
Feb 14 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 Deleted