Firefox 3.0.6 crashes on Ubuntu 8.10 when printing popup window

[ronald]

Firefox 3.0.6+nobinonly-0ubuntu0.8.10.1 is crashing with a Segmentation fault when attempting to bring up the print dialog. This is not always the case with regular printing. I'm using an internal webpage that has a hyperlink when clicked will open a .cfm file and initiate the print dialog window. As soon as the print dialog window pops up but before it is finished rendering Firefox totally closes out. The weird thing is that this will work 5 times out of 100. I do not see that a .crash file was generated.

GDB output is as follows:

---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
pure virtual method called
terminate called without an active exception

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb7c5a6c0 (LWP 22056)]
0xb7f28430 in __kernel_vsyscall ()
(gdb) Quit

[JanBrinkmann (jbrinkmann)]

Thank you very much for reporting this problem. That helps to improve the overall quality of Ubuntu! Could you please tell us which architecture you are using (for example amd64/x86?). Maybe it would be easier to debug if you could make the internal page available to the developers (maybe attach the page to this report?). Does this also happen with older releases or worked it with 3.0.5 for example? Also, please see https://wiki.ubuntu.com/MozillaTeam/Bugs#head-c576e78d92cb3c959c271158b6ace98be835de83 for an explanation on howto get a full backtrace, if possible for you.

[ronald (stonroner)]

Unfortunately I cannot provide the page as it is proprietary. I am currently using the x86 architecture.

I can provide the full backtrace and some more testing tomorrow.

[JanBrinkmann (jbrinkmann)]

Thank you very much! We're looking forward to hear from you.

[ronald (stonroner)]

I attempted to get a full backtrace using the method provided in the link but nothing was found via that method. I ran a firefox --debug and then was able to get backtrace info that way. I've included the firefox --debug gdb backtrace.

Let me know if you need anything else.

Thanks!

[JanBrinkmann (jbrinkmann)]

Thanks for the backtrace. However, there are no debugging symbols in the backtrace. They're needed to debug the problem efficiently. What in details was the problem when you use the step by step guide?

[ronald (stonroner)]

The issue I'm having with the step by step guide is related to https://bugs.launchpad.net/bugs/259900

I cannot download the debugging symbols due to version inconsistencies.

[ronald (stonroner)]

Just to note: I did change my repos to Intrepid. Same issue.

[JanBrinkmann (jbrinkmann)]

Ok, thank you very much for taking the time to respond and help out with the debugging process and such. Can you try one last thing? Try to reproduce it using a new profile. See the following URL for details:

https://wiki.ubuntu.com/MozillaTeam/Bugs?action=show&redirect=DebuggingFirefox#Try%20with%20a%20new%20profile

Thanks in advance!

[William Miller (w1miller)]

I have the same problem with Firefox 3.0.8

[Monkey (monkey-libre)]

Does Anyone still have this bug?. Thank You for making Ubuntu better.

[Monkey (monkey-libre)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, 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!