I've noticed this issue yesterday, and only once, but apparently Timothy and Gavin have also been seeing it. I noticed it when I was loading a bug page. The title of the tab was only partly visible, like "Bug 123...", and the 'u' character was mispainted in a strange way (I can't tell how exactly), and as soon as the page was done loading, the Bugzilla Tweaks jetpack's load handler kicked in, and changed the title to "123456...", which caused a repaint and fixed the problem.

My tabs are also overflowed, so the titles are cropped. I usually see this manifest as the tab title being stuck at "Connecting..." after switching away from it while it was loading (favicon is correct). Switching back to it fixes it.

This isn't Bug 571918 (i.e. Personas Usage)?

(In reply to comment #2) > My tabs are also overflowed, so the titles are cropped. I usually see this > manifest as the tab title being stuck at "Connecting..." after switching away > from it while it was loading (favicon is correct). Switching back to it fixes > it. Hmm, I can reproduce it consistently. 1. Open two tabs side by side. 2. In one of them, load a web page which is going to load slowly. As soon as you initiate the load, switch to the other tab. 3. Remain on the other tab until the load on the first tab finishes. The string "Connecting" is still shown on the title. Now, force a repaint on the title (by hovering it for example). The correct title of the tab gets painted.

(In reply to comment #3) > This isn't Bug 571918 (i.e. Personas Usage)? No, I'm not using a persona.

I can easily reproduce this on Windows as well. A good example of a slow loading web page is a huge bugzilla query.

I wonder if this is related to bug 632641.

I cannnot reproduce this on Windows 7 with D3D9

Nor with BasicLayers.

I've seen this once on Windows 7 with no HW acceleration.

Here's a different manifestation. It only happens on today's nightly (2/10), but I believe it's probably the same problem but now triggered by bug 631698 which landed yesterday http://grab.by/8TDR STR: - On non-maximized mode, have enough tabs to overflow the tab bar - The selected tab should be the add-on manager (but it shouldn't be the last one) - scroll the tab bar with the scrollwheel

If you can't reproduce with comment 11 try disabling HW accel and/or DW. The bisect on bug 632641 (which could be related) pointed to my driver being blocklisted. obs: I haven't been able to reproduce with the STR from comment 4

Regression range for me http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5bf94fcd5115&tochange=4c62984f12d1

(In reply to comment #14) > Regression range for me > http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5bf94fcd5115&tochange=4c62984f12d1 Nothing obvious jumps out at me from that list. My best guesses are: http://hg.mozilla.org/mozilla-central/rev/1e03f7e81637 http://hg.mozilla.org/mozilla-central/rev/4c62984f12d1 http://hg.mozilla.org/mozilla-central/rev/fffaf649c714

Narrowed range http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=16cc18d74a8c&tochange=4c62984f12d1 so most likely bug 508816.

This is probably fixed by the patch to bug 632379, but I can reproduce in an unpatched build only sporadically with the STR from comment 4, and not at all with the STR from comment 11. Can someone confirm?

Fixed for me in todays nightly.

I could still reproduce the problem in comment 11 after this landed, but it has been hidden by the landing of bug 633360. I think we can call that part as WORKSFORME and I'll file a new bug if I see it happening again