-
Bug
-
Resolution: Unresolved
-
Major
-
Google Chrome 26.0.1410.65 (Official Build 193261)
OS Mac OS X
WebKit 537.31 (@147513)
JavaScript V8 3.16.14.11
Flash 11.7.700.169
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31
Command Line /Applications/Google Chrome.app/Contents/MacOS/Google Chrome -psn_0_17293437 --flag-switches-begin --enable-expose-for-tabs --enable-experimental-extension-apis --sync-keystore-encryption --flag-switches-end
Executable Path /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path /Users/rburhum/Library/Application Support/Google/Chrome/Default
Variations 853359fa-33ba05a4
5f9f065f-15eb91be
b03ddc1f-2d9ef0cc
f9b252d0-fd526c81
ca6785ad-766fa2d
3709139-766fa2d
ff3fc1a6-766fa2d
d86b76a4-d674141c
7f6da4bf-cda32b90
75f7fb7e-611a9f49
24dca50e-837c4893
ca65a9fe-91ac3782
82d91892-3d47f4f4
3028188e-d60b5a5f
5a3c10b5-e1cc0f14
244ca1ac-4ad60575
246fb659-75cb33fc
f296190c-19dcaa1a
4442aae2-d7f6b13c
75f0f0a0-e1cc0f14
e2b18481-6bdfffe7
e7e71889-e1cc0f14Google Chrome 26.0.1410.65 (Official Build 193261) OS Mac OS X WebKit 537.31 (@147513) JavaScript V8 3.16.14.11 Flash 11.7.700.169 User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 Command Line /Applications/Google Chrome.app/Contents/MacOS/Google Chrome -psn_0_17293437 --flag-switches-begin --enable-expose-for-tabs --enable-experimental-extension-apis --sync-keystore-encryption --flag-switches-end Executable Path /Applications/Google Chrome.app/Contents/MacOS/Google Chrome Profile Path /Users/rburhum/Library/Application Support/Google/Chrome/Default Variations 853359fa-33ba05a4 5f9f065f-15eb91be b03ddc1f-2d9ef0cc f9b252d0-fd526c81 ca6785ad-766fa2d 3709139-766fa2d ff3fc1a6-766fa2d d86b76a4-d674141c 7f6da4bf-cda32b90 75f7fb7e-611a9f49 24dca50e-837c4893 ca65a9fe-91ac3782 82d91892-3d47f4f4 3028188e-d60b5a5f 5a3c10b5-e1cc0f14 244ca1ac-4ad60575 246fb659-75cb33fc f296190c-19dcaa1a 4442aae2-d7f6b13c 75f0f0a0-e1cc0f14 e2b18481-6bdfffe7 e7e71889-e1cc0f14
After using Chrome for a day, the page renders incorrectly.
Screenshot: http://imgur.com/9Y11bqz
It doesn't matter if I hit refresh multiple times, it always renders the same way. If I open another browser, it works fine.
If I debug under Chrome Dev Tools, I don't see any errors when fetching the resources... just a whole bunch of 304s.
If I clear the cache manually using the Chrome Web settings, then everything works fine again.
I went to #jenkins on freenode and apparently other people were having the same issue.
*Update* I can make the error go away by simply clearing the jenkins cookie and leaving the rest of the cache intact. It seems the error is session related (all the cookie contains is a session id).
I am using the GitHub plugin for authentication/authorization.
- is duplicated by
-
-
- Resolved
-
[JENKINS-17684] Dashboard web pages don't render correctly in Chrome because of bad cache/session
Ragi Burhum
created issue -
Same problem here with Google Chrome, Version 26.0.1410.64 m under Windows 7, 64-bit.
Can't enforce the bug, but it happens quite regularly after automatic refresh ran in the background for a while. Agree that it looks like a problem with CSS. Maybe a bug of Chrome, not necessarily Jenkins.
Ragi Burhum
added a comment - I can get it to happen without having automatic refresh for awhile. After the site goes into a bad state, it remain so.
I was also told (in IRC) to look at the contents of screen.css. I don't see any screen.css file though.
*I found something interesting though*. If I delete the jenkins cookie and open the page again, the page starts working again. The cookie contains the session value, so it seems that the error is related to a session id expiring. I am using the GitHub plugin for authentication/authorization.
Ragi Burhum
added a comment - I can get it to happen without having automatic refresh for awhile. After the site goes into a bad state, it remain so.
I was also told (in IRC) to look at the contents of screen.css. I don't see any screen.css file though.
* I found something interesting though *. If I delete the jenkins cookie and open the page again, the page starts working again. The cookie contains the session value, so it seems that the error is related to a session id expiring. I am using the GitHub plugin for authentication/authorization. Ragi Burhum
added a comment - I am going to update the main bug description to account for this. Ragi Burhum
made changes -
| Description |
Original:
After using Chrome for a day, the page renders incorrectly. Screenshot: http://imgur.com/9Y11bqz It doesn't matter if I hit refresh multiple times, it always renders the same way. If I open another browser, it works fine. If I debug under Chrome Dev Tools, I don't see any errors when fetching the resources... just a whole bunch of 304s. If I clear the cache manually using the Chrome Web settings, then everything works fine again. I went to #jenkins on freenode and apparently other people were having the same issue. |
New:
After using Chrome for a day, the page renders incorrectly. Screenshot: http://imgur.com/9Y11bqz It doesn't matter if I hit refresh multiple times, it always renders the same way. If I open another browser, it works fine. If I debug under Chrome Dev Tools, I don't see any errors when fetching the resources... just a whole bunch of 304s. If I clear the cache manually using the Chrome Web settings, then everything works fine again. I went to #jenkins on freenode and apparently other people were having the same issue. **Update** I can make the error go away by simply clearing the jenkins cookie and leaving the rest of the cache intact. It seems the error is session related (all the cookie contains is a session id). I am using the GitHub plugin for authentication/authorization. |
| Summary | Original: Dashboard web pages don't render correctly in Chrome because of bad cache | New: Dashboard web pages don't render correctly in Chrome because of bad cache/session |
kutzi
added a comment - Seeing something similar quite frequently (Jenkins ver. 1.480.2, Chrome Version 26.0.1410.64)
I can resolve it by forcing a full reload (CTRL+SHIFT+R)
kutzi
added a comment - Seeing something similar quite frequently (Jenkins ver. 1.480.2, Chrome Version 26.0.1410.64)
I can resolve it by forcing a full reload (CTRL+SHIFT+R) 
Michael Prokop
added a comment - Seeing the same problem here on Jenkins v1.512 + Chrome 26.0.1410.43-r189671, ctrl-shift-r works around the issue.
Might be related to JENKINS-17526?
Michael Prokop
added a comment - Seeing the same problem here on Jenkins v1.512 + Chrome 26.0.1410.43-r189671, ctrl-shift-r works around the issue.
Might be related to JENKINS-17526 ? Ragi Burhum
added a comment - To clarify:
- hitting 'refresh' does not fix it.
- Command-R ('regular' refresh), does not fix it.
- Command-Shift-R (refresh & ignore cache) temporarily makes the problem go away. It comes back after some time (less than a day).
It does look like it is similar to JENKINS-17526
Ragi Burhum
added a comment - To clarify:
hitting 'refresh' does not fix it.
Command-R ('regular' refresh), does not fix it.
Command-Shift-R (refresh & ignore cache) temporarily makes the problem go away. It comes back after some time (less than a day).
It does look like it is similar to JENKINS-17526 
Pedro Rodriguez
made changes -
| Link |
New:
This issue is duplicated by |
If anyone else sees a similar issue, please attach your screenshots as well.
http://imgur.com/9Y11bqz has no table borders, which indicates that style.css isn't kicking in. The chrome dev output indicates that Jenkins had sent 304 without content, which then makes me wonder what Chrome thinks it has in its cache.
One would think somehow the cache gets poluted, and Chrome isn't even noticing that because the server keeps sending 304 to the client.