User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b8) Gecko/20100101 Firefox/4.0b8 Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b8) Gecko/20100101 Firefox/4.0b8 Clicking tab groups button sometimes crashes the X server, but sometimes it works just fine. I haven't seen a pattern as to when it is more likely to crash, but it happens at least 1 in 10 times it is clicked. Reproducible: Sometimes Steps to Reproduce: 1. Create tabs and tab groups 2. Click the tab group button 3. Repeat until it crashes Actual Results: Crashes X server. Expected Results: Doesn't crash X server. My graphics card is an ATI Radeon HD 4850. I am using Catalyst 10.10 drivers and Xorg 1.9.2 on Arch Linux 64-bit.
This probably has something to do with the close group animation, right?
Yeah it'll be a problem in the driver or the X server, but Firefox 4 is the only program that I use that triggers it. It happens immediately after releasing the mouse button, so just as the animation starts.
Can you please test with a latest nightly build you can find under the following location? I assume that this is already fixed. http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/
Component: Tabbed Browser → TabCandy
QA Contact: tabbed.browser → tabcandy
If it's related to WebGL I would assume it is fixed by bug 624390.
Version: unspecified → Trunk
I'm using panorama intensively on Linux and this has never happend to me. I'm using Ubuntu with an Nvidia graphic card.
Sounds like it's fixed? If not, please re-open.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
I just installed beta 9 and the bug is still there.
(In reply to comment #7) > I just installed beta 9 and the bug is still there. Could you please try a nightly build?
I tried the nightly build and it didn't seem to crash.
(In reply to comment #9) > I tried the nightly build and it didn't seem to crash. If you do run into this failure again on a nightly or beta 10, do let us know.
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.