"non-crasher" here...

i'm using no themes/extensions, but i'm using the flash plugin (7,0,25,0)...

so basically i have these two files in my firefox dir:
other than that it's a clean and pristine firefox...

i upgraded to 1.0.3 the same day patrick released the packages into current... before that i might have experienced one or maybe two crashes during all my time with 1.0.1 and 1.0.2, but i was using a theme and a couple extensions when that happened... absoloutely zero crashes so far with a clean 1.0.3...

To ask people if they are using extensions I think is sometimes disrespectful because keep in mind that this is a Linux forum and most of us know better then to trust 3rd Party extensions to things. I'm talking it crashes after a fresh install with nothing added to it and the settings being fresh.

WTF???

keep your pants on, no need to go hysteric.. d:

drakethegreat: if you consider it disrespectful, you should have provided the neccesary debug info in the first place. No need to go pointing fingers when youre asked for it.

We still need more info from the people having crashes, so untill then there aint much to do about the matter..

I was getting a weird Firefox Lockup where the screen would "shimmer" and the mouse and keyboard would go dead. When I tried to compile my own version of FF-1.0.3 it said I was missing libidl. Since replacing libidl it compiled and has been very stable.

Given that libidl was moved recently I wonder if this could be part of the problem?

From the Change log

I've also had trouble with firefox segfaulting out of no where, I guess it's an extension plugin, but i can't be sure (slack current)

I never had a problem with Firefox using downloaded from mozilla.org or using Slackware package. The only temporary "hangups" where due to some third party player like Flash or using Java Web Start.

libidl was moved from gnome because gnome is no longer on current and mozilla needs that library. Has nothing to do with fixes.

This is the original "crasher".

Thanks everybody for valuable input. Sorry I went to sleep (different time zone) so I cannot answer on time.

Yes I have lots of plugins loaded but no theme. I did not have flash or Java plugin, and have Javascript disabled (I have some concerns for active contents, generally I don't use them). However, I also tried to load the official firefox build clean, it also crashes. I have not tried to load slackware package clean though.

I will run firefox from console and check what happened. Talk-back will primarily generate stack trace. I've checked some 2.6.11.7 reports, I cannot find any fix pattern. I wish I have time to use the power of source :)

I'm in office now. I'll run these tests once I get home.

shepper's post gives me lots of hope. Thank you very much! Could you please shed more light on Firefox compilation. I found some document on Firefox site about compilation, is that what you followed? Any catches?

I compiled in /usr/local and made a /user/local/foxbuild "build directory"

Then get the firefox source code and extract and uncompress in /usr/local.

This is my .mozconfig file:

Save it as .mozconfig in /usr/local/mozilla/
Then edit the path of the line "ac_add_options --with-default-mozill-five-home=/***""
to your present mozilla package.
Then from /usr/local/mozilla run "gmake -f client.mk build" followed by "gmake -C /usr/local/foxbuild/browser/installer"

If you are missing any important libaries it will tell you. The finished tarball will be in the build directory under /usr/local/foxbuild/dist. I copy the tarball over to /usr/lib and tar xvzf firefox*.tar.gz. To start it does need the full path /usr/lib/firefox/firefox.

edited mozilla path

From my understanding the Latest Trunks of firefox have been very unstable. I use them all the time and had to revert to the 22nd trunk installer. The bug is for the EM not working, since they have updated the EM controls and code. Apparently the last nightly is also missing the QFA of which I depend on for talkback for the coders so they can see the actual errors and not have someone like me, who does not exactly describe it in detail. Also they have finally gotten on the CVS bandwagon after a Year.

Slackere updates, use gFTP to get all the latest and then the new GCC++ 4.0.0 is out and I have it, but need to compile and install it. Will let you know how well it works.

http://img52.exs.cx/img52/2336/favicon.png

Hi, shepper, thank you very much for firefox compile instruction. I will try it this weekend.

I did lots of test with firefox 1.0.3 in the past 3 hours. It's a official build, loaded clean, with just a few bookmarks created and the following settings:
- Javascript/Java support disabled
- "Software Install" disabled

I tested with the following kernels:
- Stock 2.4.29 kernel of 10.1
- Stock 2.6.10 kernel of 10.1
- 2.6.11.7 kernel I compiled

I can crash firefox with a very special scenario:
1. Have bookmark panel opened;
2. Use search box of the bookmark panel to find out the site to visit;
3. Search (in bookmark panel) and open several sites simultaneously in tabs ... you have to type quickly to make that happen ... slow internet connection may also help (I use ADSL advertised as 512K).

I use the following two sites for test:
1. http://slashdot.org/
2. http://news.sina.com.cn/ (Sorry, this is not an English site)

Here's my test step:
1. Search in bookmark and find the first site, click middle mouse button to open it in a tab;
2. Search in bookmark and find the second site, click middle mouse button to open it in a tab;
3. Repeat the above two steps (without particular order) several times, as quickly as possible.

firefox will become very slow at first, and crash soon. Here's what I got on the console (just one line for each crash):
Other than the particular test I described above, I can hardly crash firefox. I have tried:
- Open many sites without search in bookmark panel;
- Search and open English sites: I've tried Slashdot, MS site, Amazon, Yahoo etc.
- Install extensions I use one by one;
- Modify firefox settings one by one, until the settings became the same as what I use daily.

I hope I can isolate a kernel/extension/setting/site that will make 1.0.3 crash. Well, as you can see, I cannot find one, except that very particular scenario I mentioned above.

You may wonder how did I pick that scenario. Well, that's my habit :) Fire up firefox, check some local news and ... Hmmm .... nerds news. I have a large bookmark, so I use bookmark search frequently.

It looks like this thread does not belong here. It definitely an application specific problem.

I've only had a few crashes with 1.0.3 using 2.6.10. It ended up being my realplayer plugin that was causing it. Looking at those seg faults you're getting, I used to get those often with 1.0.1. It ended up being a gtk issue. If you want to try a firefox version without gtk,xft and freetype, give these a try. Might help narrow down the problem.

I solved my Firefox crash problem with the latest trunk build.

I installed the latest trunk build (Gecko/20050507 Firefox/1.0+) just now and ran lots of tests. I think this build is as stable as Firefox 1.0.2 (on my system). So my firefox crash problem can be considered solved. Root cause is still unknown.

I have tried to build Firefox myself follows shepper's instruction, but that does not solve the crash problem.

Now crash has gone, but lots of other nuisance turned up. Well, this is not the correct forum for them.

Thanks, everybody :)