Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17684

Dashboard web pages don't render correctly in Chrome because of bad cache/session

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • core

      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.

        1. css_issue
          238 kB
        2. css_issue.jpg
          css_issue.jpg
          238 kB
        3. jenkins_broken_stylesheet.png
          jenkins_broken_stylesheet.png
          129 kB
        4. jenkins_css_3.PNG
          jenkins_css_3.PNG
          84 kB
        5. jenkins-chrome-scroll.JPG
          jenkins-chrome-scroll.JPG
          104 kB
        6. jenkins-gui.png
          jenkins-gui.png
          69 kB

          [JENKINS-17684] Dashboard web pages don't render correctly in Chrome because of bad cache/session

          Ragi Burhum created issue -

          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.

          Kohsuke Kawaguchi added a comment - 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.

          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.

          Lars Rosenboom added a comment - 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 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)

          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 JENKINS-17526 [ JENKINS-17526 ]

            accountapp Account App Run by Kohsuke
            rburhum Ragi Burhum
            Votes:
            24 Vote for this issue
            Watchers:
            46 Start watching this issue

              Created:
              Updated: