After a while of using Chromium, or of using other webbrowsers which use Chromium's backend, the browser crashes, and stops displaying any webpages on any browser
Reported by
iain.h.m...@gmail.com,
Jun 12 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.9.0 Chrome/56.0.2924.122 Safari/537.36 Example URL: Various, it seems to be independent of aK specific webpage. Steps to reproduce the problem: 1. use the browse in typical manner for an indeterminate ammount of time 2. at some point during use, click on a web link, could be any web link, and experience the issue 3. a hardware restart is required to resolve the issue. What is the expected behavior? The new webpage will load fully. What went wrong? Typically the browser renders a white screen instead of the full webpage. If I enter fullscreen mode and then exit fullscreen mode, the page renders as an image, although I am unable to scroll downwards (beyond around 5-10 pixels up & down) or click on any links. Once or twice the page has rendered but attempting to scroll downwards has the effect of changing the orientation of the website. Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? No qutebrowser 0.10.1-1, qupzilla 2.1.2-3, Google Chrome 59.0.3071.86-1 Chrome version: 56.0.2924.122 Channel: stable OS Version: 59.0.3071.86-1 Flash Version: First experienced on qutebrowser when using the webengine backend, later realised also present in other browsers sharing that engine. Opened bug there: https://bugreports.qt.io/browse/QTBUG-61355 Asked to open bug here. Any ideas?
,
Jun 12 2017
Reporter@ Are you able to reproduce this crash consistently? Could you please provide any sample crash ID's from chrome;//crashes for further investigation. Thanks!
,
Jun 12 2017
I cannot reproduce it at will, but it seems to happen after clicking a link, rather than during some inactive time of browsing/reading. I will try to provide those crash ID's (although I think the UI becomes unusable after the issue occurs). If the crash happens when using the browsers which are making use of the chromium backend, should I report those too? Thanks!
,
Jun 12 2017
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 14 2017
Okay, so it just happened again. The UI on chromium is basically unusuable, but I have managed to visit chrome;//crashes. Sadly, the message is that "Crash reporting is disabled" Anything else I can try?
,
Jun 14 2017
https://youtu.be/0ZxLLIXjWvk Here is a video of the bug.
,
Jun 14 2017
After a suggestion here https://bugreports.qt.io/browse/QTBUG-61355?focusedCommentId=360945& page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-360945 I just started Chromium from the terminal with "chromium --disable-gpu" and and am able to use the browser.
,
Jun 14 2017
,
Jun 16 2017
@iain: Can we close this issue as per comment #8? Thanks!!
,
Jun 18 2017
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 18 2017
I'm not sure. Does the fact that I am able to successfully start Chromium using software rendering mean that the bug lies not with Chromium but with the Intel GPU drivers? (which I am using) Thanks!
,
Jun 19 2017
,
Jun 19 2017
@iain.h.maxwell -- Thank You for the reply. To confirm whether the issue is with the drivers or with browser, perform the same steps using Firefox which would help in identifying the issue, whether it is with the driver or browser. If the issue is not reproducible in Firefox, please provide the screen cast for the behavior in Chrome and also provide the GPU details of your machine. Thanks in Advance.
,
Mar 9 2018
Closing due to lack of feedback. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by nyerramilli@chromium.org
, Jun 12 2017