Segmentation fault when intercepting navigation
Reported by
furstenh...@gmail.com,
Oct 21 2017
|
|||||
Issue description
Chrome Version : Google Chrome 62.0.3202.62
URLs (if applicable) :
Other browsers tested:
What steps will reproduce the problem?
(1) Install chrome remote interface npm i chrome-remote-interface
(2) Run stable google: google-chrome-stable --remote-debugging-port=9222 (it also fails with the --disable-gpu flag)
(3) Enter CLI for remote interface: node_modules/.bin/chrome-remote-interface inspect
(4) Network.requestIntercepted(({interceptionId, request}) => {try {Network.continueInterceptedRequest({interceptionId})} catch (e) {console.error(e)}})
(5)Network.setRequestInterceptionEnabled({enabled: true})
(6) Page.navigate({url: 'https://github.com'})
What is the expected result?
I'd expect the browser to navigate to github
What happens instead?
Browser seems to hang for a couple of seconds, then it closes with a segmentation fault. The logs are:
$ google-chrome-stable --remote-debugging-port=9222 --disable-gpu
[7045:7084:1021/114827.287294:ERROR:nss_util.cc(725)] After loading Root Certs, loaded==false: NSS error code: -8018
DevTools listening on ws://127.0.0.1:9222/devtools/browser/43e3e311-e8ce-4696-a91c-08c3401e6dfe
[7045:7045:1021/114828.457037:ERROR:account_tracker.cc(328)] OnGetTokenFailure: Invalid credentials.
[7045:7045:1021/114828.457066:ERROR:account_tracker.cc(328)] OnGetTokenFailure: Invalid credentials.
[1:16:1021/114830.522490:ERROR:adm_helpers.cc(62)] Failed to query stereo recording.
Segmentation fault (core dumped)
Please provide any additional information below. Attach a screenshot if
possible.
,
Oct 23 2017
,
Oct 23 2017
,
Nov 21 2017
Does this reproduce well? I can't reproduce so far on 62.0.3202.94. furstenheim, would it be possible for you to provide the stack trace from the core?
,
Nov 26 2017
Yes, it reproduces systematically. Where can I find the stack trace from the core? I've added --enable-loggging --v=1 and the only difference is: [8017:8017:1126/111120.796310:ERROR:buffer_manager.cc(453)] [.DisplayCompositor-0x3a1bb7e0d600]GL ERROR :GL_INVALID_ENUM : glBufferData: <- error from previous GL command
,
Dec 29
We fixed a bunch of crashes in the interception since the time this bug has been filed, so I believe this is likely gone. If not, please re-open or file again, providing a stack crash or crash report id (check chrome://crashes for the list of recent crashes, or run chrome under gdb). |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dvallet@chromium.org
, Oct 23 2017Components: Platform>DevTools>Network