firefox crashed

usr/lib/firefox/firefox-bin.1000.crash report (the entire file was 32 MB)
---------------------------------
ProblemType: Crash
Architecture: i386
Date: Sun Jul 29 00:32:49 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/firefox/firefox-bin
ProcCmdline: /usr/lib/firefox/firefox-bin http://en.wikipedia.org/wiki/Dan_Millman -a firefox
ProcCwd: /home/hobbit
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 LC_TIME=tr_TR.utf8
ProcMaps:
 08048000-0805b000 r-xp 00000000 03:01 413245 /usr/lib/firefox/firefox-bin
 0805b000-0805d000 rw-p 00012000 03:01 413245 /usr/lib/firefox/firefox-bin
 0805d000-0c404000 rw-p 0805d000 00:00 0 [heap]
 ad773000-ad774000 ---p ad773000 00:00 0
 ad774000-adf74000 rwxp ad774000 00:00 0
 adf74000-ae177000 rw-p adf74000 00:00 0
 ae1bd000-ae1ea000 r-xp 00000000 03:01 869947 /usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/i386/libjavaplugin_nscp.so
 ae1ea000-ae1f0000 rw-p 0002d000 03:01 869947 /usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/i386/libjavaplugin_nscp.so
 ae1f0000-ae396000 r-xp 00000000 03:01 457219 /usr/lib/Adobe/Acrobat7.0/Browser/intellinux/nppdf.so
 ae396000-ae3b6000 rw-p 001a6000 03:01 457219 /usr/lib/Adobe/Acrobat7.0/Browser/intellinux/nppdf.so
 ae3b6000-ae3bc000 rw-p ae3b6000 00:00 0
 ae3bc000-ae3fd000 r-xp 00000000 03:01 832526 /usr/lib/mozilla/plugins/mplayerplug-in.so
 ae3fd000-ae3ff000 rw-p 00040000 03:01 832526 /usr/lib/mozilla/plugins/mplayerplug-in.so
 ae3ff000-ae440000 r-xp 00000000 03:01 832528 /usr/lib/mozilla/plugins/mplayerplug-in-wmp.so
 ae440000-ae442000 rw-p 00040000 03:01 832528 /usr/lib/mozilla/plugins/mplayerplug-in-wmp.so
 ae4b4000-ae4f4000 r-xp 00000000 03:01 832532 /usr/lib/mozilla/plugins/mplayerplug-in-rm.so
 ae4f4000-ae4f6000 rw-p 00040000 03:01 832532 /usr/lib/mozilla/plugins/mplayerplug-in-rm.so
 ae4f6000-ae4f7000 ---p ae4f6000 00:00 0
 ae4f7000-aecf7000 rwxp ae4f7000 00:00 0
 af4f8000-af4f9000 ---p af4f8000 00:00 0
 af4f9000-afcf9000 rwxp af4f9000 00:00 0
 afcf9000-afcfb000 r-xp 00000000 03:01 374920 /lib/libnss_mdns4_minimal.so.2
 afcfb000-afcfc000 rw-p 00001000 03:01 374920 /lib/libnss_mdns4_minimal.so.2
 afe60000-b0509000 r--p 00000000 03:01 602980 /usr/share/icons/gnome/icon-theme.cache
 b0509000-b050a000 ---p b0509000 00:00 0
 b050a000-b0d0a000 rwxp b050a000 00:00 0
 b0d0a000-b0d0b000 ---p b0d0a000 00:00 0
 b0d0b000-b150b000 rwxp b0d0b000 00:00 0
 b1596000-b15d6000 r-xp 00000000 03:01 832530 /usr/lib/mozilla/plugins/mplayerplug-in-qt.so
 b15d6000-b15d8000 rw-p 00040000 03:01 832530 /usr/lib/mozilla/plugins/mplayerplug-in-qt.so
 b15fe000-b15ff000 ---p b15fe000 00:00 0
 b15ff000-b1dff000 rwxp b15ff000 00:00 0
 b1dff000-b1e00000 ---p b1dff000 00:00 0
 b1e00000-b2600000 rwxp b1e00000 00:00 0
 b2600000-b2700000 rw-p b2600000 00:00 0
 b276d000-b2771000 r-xp 00000000 03:01 374801 /lib/tls/i686/cmov/libnss_dns-2.5.so
 b2771000-b2773000 rw-p 00003000 03:01 374801 /lib/tls/i686/cmov/libnss_dns-2.5.so
 b2773000-b27ad000 r-xp 00000000 03:01 408411 /usr/lib/firefox/libnssckbi.so
 b27ad000-b27b7000 rw-...

Thank you Hobbittr 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/129683/+addcomment

I pasted the first part of the /var/crash/ report in the comments section. The original crash report, before I removed all the extensions and "cleansed" my FireFox was over 32 MB. This one is 6.6 MB and I have had trouble uploading it to your site.

I might be able to email it to you if you can accept it that way.

In the meantime I am downloading firefox-dbg and will follow the instructions in [1].

I told you that I have NO extensions, I removed them all and I listed my plugins in the original report but will list them again below:
My current plugins: (after removal of sun java)
QuickTime Plug-in 6.0 / 7 (File name: mplayerplug-in-qt.so - mplayerplug-in 3.31)
RealPlayer 9 (File name: mplayerplug-in-rm.so - mplayerplug-in 3.31)
Windows Media Player Plugin (File name: mplayerplug-in-wmp.so - mplayerplug-in 3.31)
mplayerplug-in 3.31 (File name: mplayerplug-in.so - mplayerplug-in 3.31)
Adobe Reader 7.0 (File name: nppdf.so)
Shockwave Flash (File name: libflashplayer.so - Shockwave Flash 9.0 r31)

When I tried to run: "Obtain a backtrace from an apport crash report (using gdb)" my Firefox hung up and did nothing and started to use 100% of system resources. I will attach the following files:
gdb-firefox.log AND gdb-firefox.log_did_not_work_output
The second file is what the terminal showed during and after FF locked up.

I then forced FF to quit. I reopened it normally and tried to go to AddOns and FF IMMEDIATELY quit!! I then ran the g"db against the coredump file included in the crash report that was generated when firefox crashed" and I had success. I will upload the gdb.log file also.

I hope you can help, my FF works but very strange and without my AddOns it is not useful to me. Opera is OK but it is still not like FF...

Hilario

What is the result of this bug report?

I had a lot of problems with 7.04 Ubuntu and I could never find a forum
or bug report to help me resolve them. I finally trashed 7.04 and went
back to 6.10 Ubuntu. My updated Firefox works just fine now

Thanks

Hobbit

Hilario J. Montoliu (hjmf) wrote:
> Thank you Hobbittr 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/129683/+addcomment
>
>
> ** Summary changed:
>
> - FF 2.0.0.6 crash "Segmentation fault (core dumped)"
> + firefox crashed
>
> ** Description changed:
>
> Binary package hint: firefox
> +
> + ... FF 2.0.0.6 crash "Segmentation fault (core dumped)"
> +
>
> 7.04 Ubuntu, after update to 2.0.0.6, NO problems with previous FF version (2.0.0.5)
> Firefox crashes when trying to update addons
> +
> EVERY time I try to access ANY page in https://bugs.launchpad.net/...
> +
> When I try to use the new Bug Report menu item in FF it CRASHES!!!
> (Am currently using Opera to report this)
> 1) tried to run from terminal in safe-mode -- same errors!
> 2) Deleted all addons - same errors
> 3) Deleted all themes - same errors
> 4) Deleted sun-java6-jre and all sun-java-** - same errors
> 5) Deleted entire /.mozilla/firefox directory - same errors
> 6) Did a restart of Ubuntu - same errors
>
> My current plugins: (after removal of sun java)
> QuickTime Plug-in 6.0 / 7 (File name: mplayerplug-in-qt.so - mplayerplug-in 3.31)
> RealPlayer 9 (File name: mplayerplug-in-rm.so - mplayerplug-in 3.31)
> Windows Media Player Plugin (File name: mplayerplug-in-wmp.so - mplayerplug-in 3.31)
> mplayerplug-in 3.31 (File name: mplayerplug-in.so - mplayerplug-in 3.31)
> Adobe Reader 7.0 (File name: nppdf.so)
> Shockwave Flash (File name: libflashplayer.so - Shockwave Flash 9.0 r31)
>
> ** Tags added: mt-needreport
>
> ** Changed in: firefox (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Mozilla Bugs
> Status: New => Incomplete
>

--
"Men become civilized, not in proportion to their willingness to
believe, but in proportion to their readiness to doubt. " - Ambrose Bierce

On Wed, Aug 01, 2007 at 05:09:06PM -0000, Hobbittr wrote:
>
> ** Attachment added: "gdb.log"
> http://launchpadlibrarian.net/8653125/gdb.log
>

You sure that you did step 1 (installing the -dbg packages of gtk et
al) described on https://wiki.ubuntu.com/MozillaTeam/Bugs - Crashes as well?

 - Alexander

Alexander

I believe I did but it has been a while but I tend to be anal enough
that I follow instructions to the letter if I can. If I had gotten
errors I would have reported those I think.

I apologize but time marches on and I had to get work done. I realize
this takes time to analyze but I had to do something which would work. I
hosed my "Feisty" install and reinstalled 6.10 and now everything works
great.

I think I may have not done something right in the 7.04 install, I could
not install from my LiveCD, some bug related to a second hard drive, the
solution to which I searched a lot of dark corners in vain. So I just
did a clean install of 6.10 with all the latest updates and then updated
to 7.04. That initially seemed to work. Then occasionally things
started to act squirrelly, for example, at my login screen, I had to
type the first letter twice to make the keyboard active, and other tiny,
inconsequential things which led me to a hunch and an "uh oh" that
things just were not stable.

The final straw was when the update to Firefox came down the tube and it
totally hosed on me and I had to install Opera just to have a working
browser.

So, a long story and I apologize again for any effort you may have
expended on my behalf and I really do appreciate it. I hope my bug
report was useful to someone.

John

Alexander Sack wrote:
> On Wed, Aug 01, 2007 at 05:09:06PM -0000, Hobbittr wrote:
>> ** Attachment added: "gdb.log"
>> http://launchpadlibrarian.net/8653125/gdb.log
>>
>
> You sure that you did step 1 (installing the -dbg packages of gtk et
> al) described on https://wiki.ubuntu.com/MozillaTeam/Bugs - Crashes as well?
>
> - Alexander
>

Thank you for the bug report however this report lacks information we need to investigate it further. For this reason, we are now going to close the bug report - please feel free to reopen when you have more information at hand.

Further information can be found at [1].

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs

I sent you everything you asked for, someone didn't read it or give me
further instructions for how to send what you wanted.

Close it if you wish, I was trying to help, more than the help I got
from the bug report team...

Hilario J. Montoliu (hjmf) wrote:
> Thank you for the bug report however this report lacks information we
> need to investigate it further. For this reason, we are now going to
> close the bug report - please feel free to reopen when you have more
> information at hand.
>
> Further information can be found at [1].
>
> [1] https://wiki.ubuntu.com/MozillaTeam/Bugs
>
>
> ** Changed in: firefox (Ubuntu)
> Status: Incomplete => Invalid
>

On Sat, Aug 25, 2007 at 12:59:50PM -0000, Hobbittr wrote:
> I sent you everything you asked for, someone didn't read it or give me
> further instructions for how to send what you wanted.
>
> Close it if you wish, I was trying to help, more than the help I got
> from the bug report team...
>

I am sorry, that the template used by hilario doesn't suite your
particular case so here it comes:

Crashes can depend on multiple factor ... from what I read so far it
might all be related to a hardware error on your side ... and even if
it didn't ... the procedures to extract the information we need to
properly track down crash bugs didn't yield the information needed to
process your bug; especially since you made clear that you followed the
instructions line by line, it is unlikely that we can track this issue
down without trying a lot of things manually ... which could be rather
time consuming for you and for us.

So to summarize, its not your fault at all that we couldn't get the
right information from your bug report as it is now.

If you are really willing to got into this further, we would need to
look into this through some other support channel ... you can come
into #ubuntu-mozillateam on freenode for example.

Anyway, I read that you are now happily using opera which made me
think that you don't really want to contribute that rather large
amount of time to this bug.

If I am wrong, visit us in the above support channel.

Sorry that we couldn't help you so far and thanks for your
contribution. I hope this explains a bit, why we rejected this bug
... have a nice weekend,

 - Alexander

Alexander,

Thank you for your nice reply which I am sure took away from something
far more valuable. I got snotty and should not have, I apologize.

Forums have usually been my lifeline in traversing the Linux world since
RH to Fedora Core now to Ubuntu. I love Firefox and only used Opera to
have a working browser. What I did was reverted back to Edgy from Feisty
and now everything works as I expect it to from Ubuntu. So the possible
causes of my problem may never be known. I had a lot of stability
problems when I upgraded to Feisty and it just was not worth the fight
to me. I love to play with Linux "toys" but I have other, more pressing
work to take care of and need my computer for those things.

Again thank you and good luck.

John

Alexander Sack wrote:
> On Sat, Aug 25, 2007 at 12:59:50PM -0000, Hobbittr wrote:
>> I sent you everything you asked for, someone didn't read it or give me
>> further instructions for how to send what you wanted.
>>
>> Close it if you wish, I was trying to help, more than the help I got
>> from the bug report team...
>>
>
> I am sorry, that the template used by hilario doesn't suite your
> particular case so here it comes:
>
> Crashes can depend on multiple factor ... from what I read so far it
> might all be related to a hardware error on your side ... and even if
> it didn't ... the procedures to extract the information we need to
> properly track down crash bugs didn't yield the information needed to
> process your bug; especially since you made clear that you followed the
> instructions line by line, it is unlikely that we can track this issue
> down without trying a lot of things manually ... which could be rather
> time consuming for you and for us.
>
> So to summarize, its not your fault at all that we couldn't get the
> right information from your bug report as it is now.
>
> If you are really willing to got into this further, we would need to
> look into this through some other support channel ... you can come
> into #ubuntu-mozillateam on freenode for example.
>
> Anyway, I read that you are now happily using opera which made me
> think that you don't really want to contribute that rather large
> amount of time to this bug.
>
> If I am wrong, visit us in the above support channel.
>
> Sorry that we couldn't help you so far and thanks for your
> contribution. I hope this explains a bit, why we rejected this bug
> ... have a nice weekend,
>
> - Alexander
>

--
"Men become civilized, not in proportion to their willingness to
believe, but in proportion to their readiness to doubt. " - Ambrose Bierce