New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 822343 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit 28 days ago
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Empty screen and errors in Chrome devtools on local Wordpress

Reported by lukeshar...@gmail.com, Mar 15 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0

Steps to reproduce the problem:
1. Go to a http://localhost/wordpress url

What is the expected behavior?
It should not be blank

What went wrong?
Ctrl+shift+J showed an inspector in which entering into console does not return anything. Ctrl+shift+J again shows an inspector inspector with the following errors:

Main._createAppUI: 19.928955078125ms
inspector.js:8564 Main._showAppUI: 16.073974609375ms
inspector.js:8564 Main._initializeTarget: 5.401123046875ms
2 inspector.js:6778 Uncaught (in promise) TypeError: Cannot read property 'requestContent' of undefined
    at inspector.js:6778
    at Bindings.ContentProviderBasedProject.requestFileContent (inspector.js:6778)
    at Workspace.UISourceCode.requestContent (inspector.js:6227)
    at Sources.JavaScriptBreakpointsSidebarPane._resetEntry (chrome-devtools://devtools/bundled/sources/sources_module.js:261)
    at Sources.JavaScriptBreakpointsSidebarPane.doUpdate (chrome-devtools://devtools/bundled/sources/sources_module.js:256)
    at Sources.JavaScriptBreakpointsSidebarPane.innerUpdate (inspector.js:2558)
inspector.js:4980 Cannot find context with specified id
compileScript @ inspector.js:4980
inspector.js:5505 SyntaxError: Unexpected token < in JSON at position 3
    at JSON.parse (<anonymous>)
    at contentLoaded (inspector.js:5505)
    at mycallback (inspector.js:972)
    at finishedCallback (inspector.js:976)
    at DevToolsAPIImpl.embedderMessageAck (chrome-devtools://devtools/bundled/devtools_compatibility.js:33)
    at <anonymous>:1:13

Did this work before? Yes yesterday

Chrome version: 65.0.3325.124 (Official Build) beta (64-bit)  Channel: n/a
OS Version: 16.05
Flash Version: Shockwave Flash 28.0 r0
 
Labels: Needs-Bisect Needs-Triage-M65
Labels: Triaged-ET Needs-Feedback
Tested the issue on chrome reported version 65.0.3325.124 using Ubuntu 17.10 with steps mentioned below:
1) Launched chrome reported version and navigated to URL: http://localhost/wordpress
2) On navigating to URL: http://localhost/wordpress, shows "This site can’t be reached"
Observations: Tested this issue with URL: http://localhost/wordpress, and clicked on Ctrl+shift+J and observed console didn't return anything and again clicked on Ctrl+shift+J even observed the same, console didn't shows any errors.

@Reporter: Please find the attached screen cast for your reference and provide your feedback on it. If possible could you please provide any alternate URL which reproduces the issue, it will helps us in further triaging it in better way.

Thanks!

822343.webm
7.6 MB View Download
I am not seeing this today, I am seeing another error in ctrl+shift+j ctrl+shift+j though:

Failed to load resource: net::ERR_INVALID_URL
data:text/html;base64,<!DOCTYPE html>%0A<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" prefix="og: http://ogp.me/ns#">%0A<head profile="http://gmpg.org/xfn/11">%0A<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />%0A<meta name="viewport" content="width=device-width" />%0A<meta name="apple-mobile-web-app-capable" cont... <contents of page>: http://ogp.me/ns net::ERR_INVALID_URL
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 16 2018

Cc: viswa.karala@chromium.org
Labels: -Needs-Feedback
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
Cc: sindhu.chelamcherla@chromium.org
Components: Platform>DevTools
Labels: Needs-Feedback
Unable to reproduce this issue on reported version 65.0.3325.124, on latest stable 65.0.3325.162 with link given in comment#0.

1. Launched chrome and navigated to http://localhost/wordpress, Opened devtools console -- observed blank console.
2. Hit ctrl+shift+j and opened inspectors inspector. -- Didn't observe any error.

@Reporter: Please check the video and let us know if we miss anything? Does this issue require any prior installation of any software? If possible please guide us with a video on reproducing this issue. Also does this happen only on Ubuntu 16.04? Any further information on reproducing this issue would be helpful.

Thanks!
822343_65.0.3325.124.webm
5.7 MB View Download

Comment 6 by l...@chromium.org, Apr 2 2018

Owner: lushnikov@chromium.org
Thanks for the report, and the DevTools-on-DevTools error!  The original issue description's suggests that there's some uiSourceCode that doesn't have a contentProvider.  lushnikov@ could you please take a look?  Maybe local Wordpress setups have some strange urls?

OP@, could you let us know whether you've setup mapping/persistence in your DevTools for this project?  If so, can you check whether this issue reproduces in incognito/a guest profile?
No, I hadn't set up specific mapping/persistence in Chrome beta, also I don't think I had any Chrome addons at the time. Just going to wordpress would fail and I haven't replicated the issue recently.
Project Member

Comment 8 by sheriffbot@chromium.org, Apr 2 2018

Labels: -Needs-Feedback
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
Labels: Needs-Feedback
As per comment#7 issue is not replicated by reporter.

@Reporter: Could you please confirm on closing this issue?

Thanks!
Labels: -Needs-Bisect
Status: WontFix (was: Unconfirmed)
As we are unable to reproduce the issue on latest stable 67.0.3396.62 and there is no response from the reporter from a long time, closing this issue and marking it as Won't fix.

@Reporter: Please feel to raise a new issue if there are any issues observed on the latest chrome builds.

Thanks!

Sign in to add a comment