closes when scrolling

[VinnyMonte]

Binary package hint: firefox

Firefox closes down randomly while scrolling either using wheel mouse or scroll arrows.

Logitech usb optical wheel mouse

[Peter Stickney (mrsticks)]

Just upgraded to 2.0 with Ubuntu 6.10
Was scrolling a web page with my down arrow. FF was choppy, then it just shut down.
Gnome asked me to compile a bug report. So here I am.
Running Ubuntu 6.10 on an averatec 5500 laptop.
See attached file for info.

-peter

[evanovka (evanovka)]

Similar thing for me.

using
Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.1) Gecko/20060601 Firefox/2.0.0.1 (Ubuntu-edgy)

on an averatec 4155 (... pure incidence I hope?!)

When scrolling on a page that only starts being loaded, firefox shuts down.
This is reproducible.

Once the page is loaded to some degree (to what extend exactly, I don't know), it seems to be safe to start scrolling.

Scrolling with the mouse wheel / arrows makes no difference.

[John Vivirito (gnomefreak)]

Thank you for the bug report. Could you please try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/MozillaTeam/Bugs
This will greatly aid us in tracking down your problem.

[Adam Chasen (achasen)]

Same symptom. I have dual monitor and switch to that application maximized on second screen by clicking on scroll bar. Hangs for a second and then closes.

[John Vivirito (gnomefreak)]

At the moment i am retracing the crash report. When im done i will upload it and see what can be done.

[John Vivirito (gnomefreak)]

MrSticks do you have this issue on up-to-date firefox in edgy and if so can you please attahc crash report for that version. The one you uploaded is not for latest edgy's firefox

[John Vivirito (gnomefreak)]

This is the test retrace

[Peter Stickney (mrsticks)]

I have not had this problem in a while. The version of firefox I was using at the time was whatever first shipped with Edgy at the time.

I do not currently have this problem. I am using the same hardware, same installation, with what I assume is firefox-current on edgy:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20060601 Firefox/2.0.0.1 (Ubuntu-edgy)

Sorry I couldnt be of more help in this situation.

-peter

[John Vivirito (gnomefreak)]

Thats ok MrSticks i have a good retrace of the other users crash report. Thank you for answering so fast :)

[John Vivirito (gnomefreak)]

Alexander, let me know if you need another one but i think that should do.

[Daniel T Chen (crimsun)]

(To note, I can't reproduce this using firefox-2 or firefox-3.0.)

[Jens Lehmann (jens-lehmann)]

I probably get something similar on Kubuntu 8.10. Firefox crashes randomly when scrolling a website. This is very annoying. I could get the following output when starting firefox on the command line:

----------------------------> app-startupICEDTEAPLUGIN_DEBUG = (null)
QPixmap: Invalid pixmap parameters
The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 671596 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x7fa101c449fc]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x17) [0x7fa101c44b77]
#2 /usr/lib/libX11.so.6 [0x7fa1045398c0]
#3 /usr/lib/libXrender.so.1(XRenderFreePicture+0x46) [0x7fa1047fca26]
#4 /usr/lib/libQtGui.so.4 [0x7fa0f9ec6cfb] ...

[madbiologist (me-again)]

If this is still occurring on Ubuntu/Kubuntu 11.10 please change the status of this bug from Incomplete back to Confirmed.

[Phillip Susi (psusi)]

Joshua, what release are you still having this on, and can you attach your ~/.xsession-errors after this happens?

[penalvch (penalvch)]

VinnyMonte, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install firefox-dbg && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

Please follow https://wiki.ubuntu.com/MozillaTeam/Bugs when you file this crash report so the necessary information is provided.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs