New issue
Advanced search Search tips

Issue 803393 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome stops responding after multiple page loads with CDP

Reported by jo...@purtschert.com, Jan 18 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
1. Use CDP to navigate to the websites listed in the attached file in order (non-headless mode).
2. Wait until the browser tries to navigate to "https://dailymail.co.uk".
3. The "navigate" event is sent out, but the browser stops responding

What is the expected behavior?
The browser should keep loading websites and not stop.

What went wrong?
After the following log chrome starts to shutdown:

[5130:5130:0118/094937.573240:INFO:chrome_cryptauth_service.cc(222)] Profile is not authenticated yet; waiting before starting CryptAuth managers.

Attached is the full log

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 63.0.3239.132   Channel: stable
OS Version: Ubuntu 16.04.3 LTS
Flash Version: None

This happens both in headless and non-headless mode, but for some reason at different positions in the loading process. For me, headless mode already crashes at "https://google.it".

I used Java & CDP4J to run the test. If the code is needed I can provide it.
 
website-list
970 bytes View Download
chrome_debug.log
5.1 MB View Download
Labels: Needs-Triage-M63
Components: UI>Browser
Labels: Triaged-ET TE-NeedsTriageHelp
The issue seems to be out of TE-scope as the issue need to use Java & CDP4J to run the test. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!
Status: Available (was: Unconfirmed)
Do you actually see a crash in either mode? If so, please check the ID from chrome://crashes and copy it here.
Status: Archived (was: Available)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment