Closed Bug 618612 Opened 15 years ago Closed 13 years ago

All versions of FF 3.6.x including 3.6.12 crashes almost immediately after opening

Categories

(Firefox :: General, defect)

Sun
Solaris
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: jpawlan, Unassigned)

References

()

Details

(Keywords: stackwanted)

User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.9.1.6) Gecko/20091202 Firefox/3.5.6 Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.9.1.6) Gecko/20091202 Firefox/3.6.x This only occurred occasionally on FF 3.5.x but with 3.6.x it is impossible to get FF to run on Sun Solaris 10 running on a single Sunblade workstation with a SPARC processor. FF opens normally then when ANY webpage is selected it may or may not display. Within 1 minute FF crashes completely with the following error message: /opt/firefox3612/run-mozilla.sh: line 131: 4489 Segmentation Fault (core dumped) "$prog" ${1+"$@"} ONLY with FF 3.6.12 I also sometimes get this alternate error message: GLib-ERROR **: gmem.c:136: failed to allocate 16 bytes aborting... Reproducible: Always Steps to Reproduce: 1. added /opt/firefox3612 to path in .cshrc 2.logout and log in to clear everything 3.run firefox from cmd line in a terminal window Actual Results: see error messages above. FF 3.5.x intermittently crashed with error message but not often enough to report. /opt/firefox3612/run-mozilla.sh: line 131: 4489 Segmentation Fault (core dumped) "$prog" ${1+"$@"} I have since tried FF 3.6.1, 3.6.3, and now 3.6.12 and it is impossible to use because FF crashes every time within 1 minute of running it. running true Sun Solaris 10 (not opensolaris) on a Sun Blade 150 with a SPARC processor. Running locally without any remote login. Crash occurs both logged in as User and also when logged in as Root. Makes no difference.
Hi their can I ask you to try and do https://support.mozilla.com/en-US/kb/Safe%20Mode?s=safe+mode&as=s please let us know if this does not work
Status: UNCONFIRMED → NEW
Ever confirmed: true
Answer to your request: Please READ the page you suggested that I look at and follow. There is ONLY a SAFE MODE for the WINDOWS version. There is no way to select or use a safe mode in unix (SunOS - Solaris) at least that I can find.... maybe there is some special commandline option you know about that works under unix.
OS: Android → Solaris
1. why did timeless <timeless@bemail.org> change my bug report from Solaris to Android? I am not running android so please do not change my bug OS. 2. The linux command line option -safe-mode did run on Solaris and I selected "continue to run in safe mode" in the dialog box. However, running in safe mode produced the same results; FF crashed while opening the second webpage. Here is the error reported in the terminal: /opt/firefox3612/run-mozilla.sh: line 131: 6925 Segmentation Fault (core dumped) "$prog" ${1+"$@"}
i didn't change it, my buggy webkit based browser did. it likes doing that. i'm sorry. i regret using webkit browsers daily. i'm not sure about the status of solaris crash reporting, if it works, then: https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report should let you get a stack trace.
Keywords: stackwanted
Thank you for your reply and suggestions. I found that the linux stack reporting is done by adding extra packages via RPM. These are not applicable to Sun Solaris and I really do not want to break things further by searching and adding a new package which I do not know is completely safe. However, I spent the last three hours doing further testing. I found that using the safe mode and this time deleting all settings and plugins completely, I was able to get FF 3.6.12 to work most of the time. However, when I re-ran FF in normal mode and I tried to reinstall the java plugin via the normal method of creating a symbolic link, it was not "seen" by FF and would never come up. The java control panel showed that it was installed correctly. Then I went to the Mozilla Help pages and searched for java plugin problems. Surprisingly FF crashed on the Mozilla page with the same segmentation fault error and core dump as before. So I had to reload FF 3.5.6 to write this.
Please reopen if you have a stacktrace Note: Solaris is no Tier-1 platform and the builds a contributed by Oracle
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.