when I open some window web page, FireFox crash

[Osti Giancarlo]

Binary package hint: firefox

I have a lot of crash with release 3.0b.5 and I wayting the new release 3.0.

Unfortunatelly today I have soonest at the first start several crash.
Today I learned debugging rogram crash on Firefox and now I have the possibility to enclose the backtrace:

GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
(no debugging symbols found)
(gdb)
(gdb) run
Starting program: /usr/lib/firefox-3.0/firefox
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x7fb6130876f0 (LWP 6653)]
[New Thread 0x41200950 (LWP 6656)]
[New Thread 0x4264b950 (LWP 6657)]
[New Thread 0x42e4c950 (LWP 6658)]
[Thread 0x42e4c950 (LWP 6658) exited]
[New Thread 0x41a01950 (LWP 6659)]
[Thread 0x41a01950 (LWP 6659) exited]
[New Thread 0x41a01950 (LWP 6660)]
[New Thread 0x42e4c950 (LWP 6661)]
[New Thread 0x4364d950 (LWP 6662)]
[New Thread 0x43e4e950 (LWP 6663)]
[Thread 0x43e4e950 (LWP 6663) exited]
[New Thread 0x43e4e950 (LWP 6664)]
[Thread 0x43e4e950 (LWP 6664) exited]
[New Thread 0x43e4e950 (LWP 6665)]

The page in question is:

www.beppegrillo.it

but also further web pages as repubblica.it, as lastampa.it and so on. I think in the pages that are some video .flv.

I have Ubuntu 8.04 Hardy Heron - 64 bit.

Pleae be so kind to consider this bug urgently.
Thanks and regards.

PS. I have Firefox release 3.0

[Alexander Sack (asac)]

On Tue, Jun 10, 2008 at 09:14:22PM -0000, Osti Giancarlo wrote:
> Public bug reported:
>
> Binary package hint: firefox
>
> I have a lot of crash with release 3.0b.5 and I wayting the new release
> 3.0.
>
> Unfortunatelly today I have soonest at the first start several crash.
> Today I learned debugging rogram crash on Firefox and now I have the possibility to enclose the backtrace:

Please follow instructions here on how to obtain a backtrace:

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

anyway its ffox 3

 affects ubuntu/firefox-3.0
 status incomplete

and not ffox 2

 affects ubuntu/firefox
 status invalid

 - Alexander

[Osti Giancarlo (ostivalentino)]

Ok try again.

Following your indicate page of wiki.ubuntu, I have the attachment backtrace.

Hope you help.
Regards
giancarlo

[Alexander Sack (asac)]

looks like a fontconfig issue on a first glance. keeping xulrunner-1.9 until we know more.

[Osti Giancarlo (ostivalentino)]

Gentlemen,

today have made a lot of update, also regarding Firefox and xulrunner.
Open a web page (www.beppegrillo.it) and than unexpected closure. I have to restart.
I enclose the debugging backtrace if help you.
Thanks and regards.

[Alexander Sack (asac)]

On Wed, Jun 18, 2008 at 10:08:05AM -0000, Osti Giancarlo wrote:
> Gentlemen,
>
> today have made a lot of update, also regarding Firefox and xulrunner.
> Open a web page (www.beppegrillo.it) and than unexpected closure. I have to restart.
> I enclose the debugging backtrace if help you.
> Thanks and regards.
>
> ** Attachment added: "gdb-firefox.txt"
> http://launchpadlibrarian.net/15406318/gdb-firefox.txt
>

Please open a new bug for your crash. Thanks!

 - Alexander

[Pedro Villavicencio (pedro)]

the fontconfig symbols are missed, do you still got the issue? may you install the fontconfig dbgsym package and get a new backtrace ? thanks in advance.

[Alex Denvir (coldfff)]

We are closing this bug report because it has not been updated for some time. Please reopen it if you have more information to submit, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!