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

Issue 804182 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Uncaught ReferenceError: loadTimeData is not defined

Reported by hakerh403@gmail.com, Jan 21 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
Not sure.

What is the expected behavior?
No error should be thrown.

What went wrong?
Chrome's native JavaScript throws an error without any reasonable explanation. I'm uploading the script as an attachment. Notice that it is a native Chrome's script and not a user script.

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 6.3
Flash Version: /
 
1.zip
2.1 KB Download
Cc: susanjun...@techmahindra.com
Labels: Needs-Feedback Triaged-ET Needs-Triage-M63
hakerh403@ Thanks for the issue.

Tested this issue on Windows 10 and Mac OS 10.12.6 on the latest Canary 66.0.3328.0 and Stable 63.0.3239.132 by following the below steps.

1. Launched Chrome and opened the given JS file and opened Devtools and couldn't see any error in the Console tab.
2. Tried another way by opening Devtools -> Sources -> Filesystem -> Add Folder to workspace and added the given JS file.
3. Clicked on the Console tab and can see "Failed to load resource: net::ERR_FAILED" error, but couldn't see Uncaught ReferenceError: loadTimeData is not defined error.
Attached is the screen cast for reference.

Request you to please check and confirm if anything is missed from our end in reproducing the issue.

Also request you to please provide the screen cast of the steps followed where this issue can be seen, which will help in better understanding.

Thanks..


804182.webm
5.1 MB View Download

Comment 2 by hakerh403@gmail.com, Jan 22 2018

Weird. I cannot reproduce the issue now. Not sure what exactly caused it to throw an error, but I suspect it has something to do with flags. I remember that I had disabled and then re-enabled chrome://flags related to service workers. After that, the above error message started to appear randomly on arbitrary websites.

I cannot tell for sure, as I'm unable to reproduce the issue now, but it is probably some issue with Chrome. This script is not loaded by a website, instead it is a builtin Chrome's script (loaded in the background on every website) and I think it should not throw any errors.
Project Member

Comment 3 by sheriffbot@chromium.org, Jan 22 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "susanjunia.boorgula@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
As per comment#2 from the reporter, as the issue is not seen now, hence closing it.

@Reporter:
Feel free to raise the new issue with proper repro steps if the issue is seen again.

Thanks!
Cc: viswatej...@techmahindra.com
Status: WontFix (was: Unconfirmed)

Sign in to add a comment