firefox crashed

There was already filled a bug on mozilla. See https://bugzilla.mozilla.org/show_bug.cgi?id=91432
But it's from 2001, and on my firefox 2.0 on my windows xp system (I use it now) it works good.

Thank you 4nDr3s for submitting this report.

Could you please try to obtain a backtrace by following the instructions on
[1], or upload the crash report that probably was generated during the crash
and that should be located at /var/crash/ to [2].

Please indicate which extensions/plugins do you have enabled; and if this crash
is reproducible describe the steps that lead to it (it is very important for us
to have a test case for each crash).

This will greatly aid us in tracking down your problem.

Thanks in advance.

H. Montoliu

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs
[2] https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/116959/+addcomment

Hi H. Montoliu

First of all i tried creating a new profile like it says on [1]. I did this:
1. roaksoax@roaksoax-laptop:/var/crash$ firefox -ProfileManager
2. I created a new profile and launched it.
3. I entered the website that causes the crash [3].
4. After a few seconds (after it loaded the website) Firefox crashed.
5. On the terminal this was displayed after the crash:

roaksoax@roaksoax-laptop:/var/crash$ firefox -ProfileManager
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 20403 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.)

I'm not using any firefox extension... it is all default.
It didn't generate any crash report on /var/crash.
I'm using Mozilla Firefox 2.0.0.3, Copyright (c) 1998 - 2007 mozilla.org on Edgy Eft

[1]: https://wiki.ubuntu.com/MozillaTeam/Bugs
[3]: http://www.healthsystem.virginia.edu/UVAHealth/peds_derm_sp/roseola.cfm

If you need further explanation or anything else just let me know

As no report was generated, would you mind to follow this hints [1] to obtain a backtrace.

Thank you in advance.

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs/#head-c576e78d92cb3c959c271158b6ace98be835de83

Here is the report following [1] steps....

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs/#head-c576e78d92cb3c959c271158b6ace98be835de83

Sorry for the delay

On Sun, May 27, 2007 at 02:55:09AM -0000, 4nDr3s wrote:
> Here is the report following [1] steps....
>
> [1] https://wiki.ubuntu.com/MozillaTeam/Bugs/#head-
> c576e78d92cb3c959c271158b6ace98be835de83
>
> Sorry for the delay
>

No problem. Do you use beryl or something? What options do you have
configured in your /etc/X11/xorg.conf?

 - Alexander

I have beryl installed but it is not running and certanly not during firefox crashes. I'm attaching my xorg.conf

On Tue, May 29, 2007 at 08:27:45PM -0000, 4nDr3s wrote:
> I have beryl installed but it is not running and certanly not during
> firefox crashes. I'm attaching my xorg.conf
>

If you can reproduce now, please try to disable those Pixmaps options
(both or one by one).

Thanks,

 - Alexander

I reproduced it disabling Pixmaps options (both and one by one) and firefox still crashes (it closes without any notice). Do you want a backtrace with Pixmaps disabled?

Is this still an issue for you? We are trying to sort this issue and would like to know if this still happens.

If it can be reproduced, please describe the steps to do it.

Also it would be nice if you provide a stactrace of the crash.

Thanks in advance.

Hello,

I would like to say that I can't reproduce it in 2.0.0.6. Could someone confirm this?

4nd3rs, did the update fix this problem?

We have not received any duplicates for some time. Thus, this crash was likely due to some unique plugin extension combination or has been fixed in the meantime. Please, reopen it at any time if you have more related info.

Thanks for your contribution. Don't hesitate to submit new crashes,

H. Montoliu