Obsolete
Status Update
No update yet.
Comments
as...@chromium.org
[Empty comment from Monorail migration]
pf...@chromium.org
[Empty comment from Monorail migration]
vs...@chromium.org
Do you still experience this?
Can you try opening DevTools on Devtools (press Ctrl/Cmd+Shift+i in the undocked mode) next time to see if there any errors in the console?
Looks like your DevTools is stuck in some weird state which could be caused by some earlier errors in it.
Could you please try again to see if this still happens on the most recent stable version and on the Chrome Canary as well?
Can you try opening DevTools on Devtools (press Ctrl/Cmd+Shift+i in the undocked mode) next time to see if there any errors in the console?
Looks like your DevTools is stuck in some weird state which could be caused by some earlier errors in it.
Could you please try again to see if this still happens on the most recent stable version and on the Chrome Canary as well?
vs...@chromium.org
No feedback and can not repro.
jo...@gmail.com
I haven't been able to test on Chrome Canary, but the issue appears to have stopped for me at some point between now and May, when I reported it.
si...@sigfried.org
Opening DevTools on DevTools worked for me. It didn't report any problem, but when I did it and reloaded, I suddenly got the current version of my sourcemapped javascript. (My problem had been slightly different. The right version of the js file was loading in DevTools and elsewhere, but it was showing me old code in the source map display.)
si...@sigfried.org
Spoke too soon. I was looking at the raw .js, not the source-mapped version. That is still showing me stale code.
[Deleted User] <[Deleted User]>
I have this issue or something very similar with Chrome 44.0.2403.157. Devtools on Devtools shows this (though not every time):
TypeError: Cannot read property 'substring' of undefined TypeError: Cannot read property 'substring' of undefined
at Object.WebInspector.JavaScriptSourceFrame._prepareScopeVariables (chrome-devtools://devtools/bundled/sources_module.js:668)
at Object.wrappedCallback (inspector.js:6110)
at Object.remoteObjectBinder (inspector.js:6059)
at Object.InspectorBackendClass.AgentPrototype.dispatchResponse (inspector.js:3863)
at Object.InspectorBackendClass.Connection.dispatch (inspector.js:3781)
at Object.InspectorBackendClass.MainConnection._dispatchMessage (inspector.js:3806)
at Object.WebInspector.Object.dispatchEventToListeners (inspector.js:741)
at innerDispatch (inspector.js:1360)
at Object.InspectorFrontendAPIImpl._dispatch (inspector.js:1359)
at dispatch (devtools.js:1437)innerDispatch @ inspector.js:1360
TypeError: Cannot read property 'substring' of undefined TypeError: Cannot read property 'substring' of undefined
at Object.WebInspector.JavaScriptSourceFrame._prepareScopeVariables (chrome-devtools://devtools/bundled/sources_module.js:668)
at Object.wrappedCallback (inspector.js:6110)
at Object.remoteObjectBinder (inspector.js:6059)
at Object.InspectorBackendClass.AgentPrototype.dispatchResponse (inspector.js:3863)
at Object.InspectorBackendClass.Connection.dispatch (inspector.js:3781)
at Object.InspectorBackendClass.MainConnection._dispatchMessage (inspector.js:3806)
at Object.WebInspector.Object.dispatchEventToListeners (inspector.js:741)
at innerDispatch (inspector.js:1360)
at Object.InspectorFrontendAPIImpl._dispatch (inspector.js:1359)
at dispatch (devtools.js:1437)innerDispatch @ inspector.js:1360
an...@gmail.com
be...@cozycloud.cc
I have exactly the same problem.
both on chrome and chromium on the same machine.
I don't know how to get the traces of DevTools...
I am about to re-install my OS...
both on chrome and chromium on the same machine.
I don't know how to get the traces of DevTools...
I am about to re-install my OS...
[Deleted User] <[Deleted User]>
js...@gmail.com
I'm having this issue for the first time today with
Version 46.0.2490.86 (64-bit).
I tried deleting files off the filesystem, and chrome still is showing old copies of the files somehow. Firefox is working fine & doesn't have the issue.
Literally I added a console.log(), which does log to console, but clicking on it takes me to the line where I expect to see the console.log(), but its an old copy of the file without any console.log().
Its as if chrome devtools contradicts itself, the console & sources tabs contradict.
Version 46.0.2490.86 (64-bit).
I tried deleting files off the filesystem, and chrome still is showing old copies of the files somehow. Firefox is working fine & doesn't have the issue.
Literally I added a console.log(), which does log to console, but clicking on it takes me to the line where I expect to see the console.log(), but its an old copy of the file without any console.log().
Its as if chrome devtools contradicts itself, the console & sources tabs contradict.
js...@gmail.com
Clearing chrome's cache since the beginning of time fixed it, even though I've had "disable cache" checked in the network tab this whole time. There's definitely a huge bug here. Not sure what causes it.
ak...@gmail.com
Based on the comments on this thread, it looks like this bug was fixed (whether accidentally or intentionally) in mid-2014 and re-introduced in mid-2015. This is a *huge* problem for me. Version dump, if this helps:
Google Chrome 47.0.2526.106 (Official Build) (64-bit)
Revision 19b9e1a5713f4b9ae324bd59bbe16ca6eb91d0e0-refs/branch-heads/2526@{#532}
OS Mac OS X
Blink 537.36 (@19b9e1a5713f4b9ae324bd59bbe16ca6eb91d0e0)
JavaScript V8 4.7.80.25
Flash 20.0.0.267
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36
Command Line /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --enable-avfoundation --flag-switches-begin --flag-switches-end
Executable Path /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path /Users/aki/Library/Application Support/Google/Chrome/Default
Variations 47f591a-3f4a17df
b3888d8d-ca7d8d80
6345b824-3d47f4f4
e950616e-ca7d8d80
7c1bc906-f55a7974
770a425-f23d1dea
e9f4800b-39c30599
19f73432-ca7d8d80
76b48ab8-a2567007
31362330-ca7d8d80
c70841c8-4866ef6e
fb124cc-803f8fc4
1d3ad72e-3f4a17df
9e5c75f1-e1c7cd46
f79cb77b-3d47f4f4
ca65a9fe-91ac3782
4117e878-3d47f4f4
9736de91-ca7d8d80
dbffab5d-ca7d8d80
244ca1ac-4ad60575
f47ae82a-86f22ee5
3ac60855-486e2a9c
ed1d377-e1cc0f14
75f0f0a0-4ad60575
e7e71889-e1cc0f14
b39ea213-d1372334
bd368a6b-d2c8e0a4
a70306ec-f23d1dea
(for the love of god, someone please tell me if that contains PII)
Google Chrome 47.0.2526.106 (Official Build) (64-bit)
Revision 19b9e1a5713f4b9ae324bd59bbe16ca6eb91d0e0-refs/branch-heads/2526@{#532}
OS Mac OS X
Blink 537.36 (@19b9e1a5713f4b9ae324bd59bbe16ca6eb91d0e0)
JavaScript V8 4.7.80.25
Flash 20.0.0.267
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36
Command Line /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --enable-avfoundation --flag-switches-begin --flag-switches-end
Executable Path /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path /Users/aki/Library/Application Support/Google/Chrome/Default
Variations 47f591a-3f4a17df
b3888d8d-ca7d8d80
6345b824-3d47f4f4
e950616e-ca7d8d80
7c1bc906-f55a7974
770a425-f23d1dea
e9f4800b-39c30599
19f73432-ca7d8d80
76b48ab8-a2567007
31362330-ca7d8d80
c70841c8-4866ef6e
fb124cc-803f8fc4
1d3ad72e-3f4a17df
9e5c75f1-e1c7cd46
f79cb77b-3d47f4f4
ca65a9fe-91ac3782
4117e878-3d47f4f4
9736de91-ca7d8d80
dbffab5d-ca7d8d80
244ca1ac-4ad60575
f47ae82a-86f22ee5
3ac60855-486e2a9c
ed1d377-e1cc0f14
75f0f0a0-4ad60575
e7e71889-e1cc0f14
b39ea213-d1372334
bd368a6b-d2c8e0a4
a70306ec-f23d1dea
(for the love of god, someone please tell me if that contains PII)
pf...@chromium.org
@aki.kyozoku: could you please provide steps to repro the issue (ideally reliable repro)?
ak...@gmail.com
Yeah sorry I should have included this in the first place.
*OS:* Mac OS X
*Browser:* Chrome 47.0.2526.106
*Screenshot:*
**Repro Steps:**
1. Open Chrome Dev Tools on a page served by a local server
2. Change javascript file in external editor, save file
3. Reload page that has Chrome Dev Tools open
**Expected:** Javascript files in sources panel that have been generated from sourcemap reflect the change
**Actual:** Despite the actual *.map file reflecting the change, Chrome Dev Tools does not. It's so heavily cached that it doesn't recognize when new files are added, which can lead to some REALLY confusing results when there's an exception.
I'm not totally sure how to offer a reliable repro beyond saying this happens consistently on my computer. The only way to get dev tools to load a changed sourcemap is to open an incognito window. (note: this bug exists on incognito as well, of course, so i'm repeatedly opening and closing incognito windows.)
*OS:* Mac OS X
*Browser:* Chrome 47.0.2526.106
*Screenshot:*
**Repro Steps:**
1. Open Chrome Dev Tools on a page served by a local server
2. Change javascript file in external editor, save file
3. Reload page that has Chrome Dev Tools open
**Expected:** Javascript files in sources panel that have been generated from sourcemap reflect the change
**Actual:** Despite the actual *.map file reflecting the change, Chrome Dev Tools does not. It's so heavily cached that it doesn't recognize when new files are added, which can lead to some REALLY confusing results when there's an exception.
I'm not totally sure how to offer a reliable repro beyond saying this happens consistently on my computer. The only way to get dev tools to load a changed sourcemap is to open an incognito window. (note: this bug exists on incognito as well, of course, so i'm repeatedly opening and closing incognito windows.)
pf...@chromium.org
Could you please check the behavior on Chrome Canary?
pa...@chromium.org
[Empty comment from Monorail migration]
da...@gmail.com
I am having the same problem with SCSS source-mapped files. The only thing I can add is that in my case the elements I am debugging are inside an iframe.
pf...@chromium.org
Archiving the old bug, I don't think SCSS issue is relevant, please file a separate bug for it.
ch...@zetaweb.com
I'm seeing similar behavior under Chrome 51.0.2704.106 (Mac OS 10.10.5). The project I'm on uses webpack, which adds additional layers of complexity (what's this 'webpack' scheme in sourcemap (yes?) URLs?). To whittle down a test case appears daunting. :(
ch...@zetaweb.com
> Can you try opening DevTools on Devtools (press Ctrl/Cmd+Shift+i in the undocked mode) next time to see if there any errors in the console?
When I hit Cmd+Shift+i with focus on the file viewer in undocked mode, I get an OS modal asking if I want to launch a mail client.
When I hit Cmd+Shift+i with focus on the file viewer in undocked mode, I get an OS modal asking if I want to launch a mail client.
ch...@zetaweb.com
> The only way to get dev tools to load a changed sourcemap is to open an incognito window. (note: this bug exists on incognito as well, of course, so i'm repeatedly opening and closing incognito windows.)
Hmm ... perhaps this could help in whittling down a test case ...
Hmm ... perhaps this could help in whittling down a test case ...
i....@gmail.com
Almost a year later, this is still happening under 57.0.2987.133 (64-bit). No rhyme or reason; right clicking on the outdated file and selecting "Copy Link Address" yields its `file://` URI - which when opening in a text editor shows the correct version.
I feel like there is hint of doubt on whether this bug exists or not, so I made a video of it.https://www.youtube.com/watch?v=LKg0wibqtNg&feature=youtu.be
I will happily do anything necessary to help make a repro case, but I have absolutely no idea where to start.
I feel like there is hint of doubt on whether this bug exists or not, so I made a video of it.
I will happily do anything necessary to help make a repro case, but I have absolutely no idea where to start.
mi...@gmail.com
I am now in search of a another browser for development purposes. To much frustration using chrome and updating javascript/css.
Also, the chrome DNS cache caused a web application to serve an old, outdated version of an application, even after the DNS changes had propagated.
Also, the chrome DNS cache caused a web application to serve an old, outdated version of an application, even after the DNS changes had propagated.
se...@gmail.com
Still experiencing this issue. Should not be closed.
[Deleted User] <[Deleted User]>
ja...@gmail.com
This happened to me last week at work, found no fixes for it, making chrome unusable for me for development. Only happens on my work laptop.
The updated code is running, confirmed with console.logs and debugger but devtools show me the old version of the file that have no console.logs or debugger. It refers to the correct row that i put my breakpoint at, but the breakpoint is nowhere to be found in file displayed in the sources tab. Clearing cache etc still shows the old file while running the new file.
The updated code is running, confirmed with console.logs and debugger but devtools show me the old version of the file that have no console.logs or debugger. It refers to the correct row that i put my breakpoint at, but the breakpoint is nowhere to be found in file displayed in the sources tab. Clearing cache etc still shows the old file while running the new file.
go...@springtimesoftware.com
[Comment Deleted]
bm...@chromium.org
If this is still a problem, please open a new bug with detailed reproduction steps.
go...@springtimesoftware.com
My mistake. I've deleted the comment, and I will delete this one later.
pe...@gmail.com
[Comment Deleted]
pe...@gmail.com
I've been having this problem on a project that I've shared on GitHub here: https://github.com/philipswan/TetheredRing . In this project, the file "TransitSystem.js"
in particular does not update when I save it (using VScode for editing). Saving this file also does not trigger an auto reload of the project. Other files do not have this problem. In the Chrome debugger, on the sources tab, I see that another file, "launcher.js" only has "?t=1669015078917" annotated to it. This number seems to increment over time. I'm not sure if this is related to the problem, but launcher.js does not seem to have any kind of caching problem.
(Repo Note: If you're only trying to quickly reproduce the problem, I think that it might be ok to skip the time consuming "npm run dev-sync" step).
Using Chrome Version 107.0.5304.107 (Official Build) (64-bit)
Happy to help out any dev who wants to try to get to the bottom of this! You can contact me through my GitHub account. I don't monitor the gmail account I'm using to comment on this bug.
in particular does not update when I save it (using VScode for editing). Saving this file also does not trigger an auto reload of the project. Other files do not have this problem. In the Chrome debugger, on the sources tab, I see that another file, "launcher.js" only has "?t=1669015078917" annotated to it. This number seems to increment over time. I'm not sure if this is related to the problem, but launcher.js does not seem to have any kind of caching problem.
(Repo Note: If you're only trying to quickly reproduce the problem, I think that it might be ok to skip the time consuming "npm run dev-sync" step).
Using Chrome Version 107.0.5304.107 (Official Build) (64-bit)
Happy to help out any dev who wants to try to get to the bottom of this! You can contact me through my GitHub account. I don't monitor the gmail account I'm using to comment on this bug.
bm...@chromium.org
Thanks a lot! Could you please open a new bug with the steps and the repro? This was archived in 2016 and it might be a very different problem (with the same symptoms) that you are experiencing.
is...@google.com
This issue was migrated from crbug.com/chromium/369797?no_tracker_redirect=1
[Auto-CCs applied]
[Multiple monorail components: Platform>DevTools, Platform>DevTools>JavaScript]
[Monorail components added to Component Tags custom field.]
[Auto-CCs applied]
[Multiple monorail components: Platform>DevTools, Platform>DevTools>JavaScript]
[Monorail components added to Component Tags custom field.]
Description
Chrome Version : 34.0.1847.131
OS Version: Windows 8.1 Professional
URLs (if applicable) : N/A
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: Untested
Firefox 4.x: OK
IE 7/8/9: Untested
What steps will reproduce the problem?
Unfortunately, I have not been able to determine reliable reproduce steps. However, in some circumstances, certain JavaScript source files will not appear on the "Sources" tab, despite the fact that the browser is executing them (as proven by console.log statements that appear in DevTools). If you click on the filename next to the console.log output, you are taken to an old version of the JS file in question.
And you can see a video demonstration of this here:
http://www.screencast.com/t/YWaRwg5Bbb
There is a StackOverflow post (where others note they've experienced the same behavior) here:
http://stackoverflow.com/questions/23398854/chrome-developer-tools-caches-old-version-of-javascript-files
If I had to guess, it has something to do with JavaScript sourcemaps being enabled. I never encountered this behavior before I started using sourcemaps. However, I have now disabled JavaScript sourcemaps and the issue persists.
What is the expected result?
All JavaScript sources loaded and executed by the host page should be displayed in the Sources tab.
What happens instead of that?
Certain files, seemingly randomly, will not be available in the Sources tab, and if you managed to "find" a file by clicking the filename next to console.log output that was executed in that file, you will get an old, cached version of the page.
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537.36