Issue metadata
Sign in to add a comment
|
Screen goes black when clicking on "elements" on dev tools
Reported by
ren...@userlane.com,
Aug 28
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.57 Safari/537.36 Steps to reproduce the problem: 1. Open dev tools 2. Start clicking around on elements, sometimes bug only happens when you start editing the element. Also happened when editing styles, but less frequent. 3. What is the expected behavior? It should work as normal. What went wrong? When clicking on edit (most frequent trigger, causes the bug almost every time), dev tools screen AND browser screen (completely, even menu bar - the whole window) goes black for a few seconds. After that, it recovers, but the feature where mouse over on an element on dev tools highlights the element on the page is gone -sometimes. When the highlight feature is gone, closing and reopening dev tools fixes it. Did this work before? N/A Chrome version: 69.0.3497.57 Channel: beta OS Version: 10.0 Flash Version: This looks like a display error, so I have Nvidia boards. The bug happens on both my work laptop AND my desktop, so not related to the graphics board itself (and that also means you probably already got some reports). The bug has lasted for some chrome versions, and some Nvidia updates.
,
Aug 30
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 69.0.3497.57 using Windows 10 with the below mentioned steps. 1. Launched Chrome 2. Navigated to a webpage and opened DevTools 3. Initially clicked on the elements then later started editing them. We observed everything was working normally and didn't notice the screen going black. @Reporter: Could you please check the same in a new profile with out any apps & extensions and let us know if we have missed anything in the process. Any further inputs from your end may be helpful.
,
Aug 30
Just reproduced in anonymous mode, is that enough? I have to edit a few times before it happens, about 10 edits in average. Just randomly clicking and editing the dom. This happens on both my personal and work profiles, on both home and work machines. I have 3 screens in one, 2 in the other, and dev tools are always on a different screen than the browser is. I will pay attention if it happens only on specific pages or not, but from memory, it's everywhere. I am on dev tools a lot in many websites.
,
Aug 30
Wait sorry, tried reproducing on my personal profile but it doesn't crash. It still does on my work profile on anonymous mode. It's possible I never had the crash on my personal profile, sure looks so. What else can I try to isolate?
,
Aug 30
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 3
renato@ Thanks for the update. Re-tried the issue again on the Windows 10 on the reported version 69.0.3497.57 and unable to reproduce this issue as per comment #4. Request you to provide the crash ID from chrome://crashes, which will help in further triaging of the issue. Thanks..
,
Sep 3
I have 4 crash IDs, but very old, and the bug itself doesn't create a new one. Here is the latest ID: Uploaded Crash Report ID 21848859eaf03e46 (Local Crash ID: 174cb4fb-46da-4d61-aecd-81798867be47), from July 3, 2018. When reproducing the bug, it seemed to me it wasn't happening, until I opened an extension. After that, the bug happens consistently, even after a page reload.
,
Sep 3
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 4
renato@ Thanks for providing Crash ID. As per comment# 7, reporter has provided Crash ID, hence routing this issue to Inhouse for further triaging the issue and adding TE-NeedsTriageFromHYD label to it. Thanks!
,
Sep 6
Thanks for the reply renato@. Please check the issue on Windows 10 using chrome latest beta-69.0.3497.81 (uninstall old chrome & install latest build), provide us the latest 16 digit crash server id from chrome://crashes(as attached in screenshot) if still issue persists. Note: Local crash id is not enough to get info from crash server.
,
Sep 8
Sunny is this duplicate of Issue 881303 ?
,
Sep 10
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Aug 28