Closed Bug 419944 Opened 18 years ago Closed 16 years ago

Segmentation fault some times.

Categories

(Firefox :: General, defect)

2.0 Branch
x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dmitry.leonenko, Unassigned)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.11) Gecko/20080118 Ubuntu/7.10 (gutsy) Firefox/2.0.0.11 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080207 Ubuntu/7.10 (gutsy) Firefox/2.0.0.12 debug information may help. However bug is not always reproducible. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. Actual Results: Segmentation fault Expected Results: normal work Installed plugins: DOM Inspector 1.8.1.12 FireBug 1.05 Google Browser Sync 1.3.20070523.0 Google Notebook 1.0.0.19 Google Toolbar for Firefox 3.0.20070525L SQLite Manager 0.2.27 ubuntu 0.4~beta1 But crashes even with disabled plugins. It happends more often with firebug enabled and opened.
Attached file gdb log
Version: unspecified → 2.0 Branch
I have the same problem with the 2.0.0.13 version of Firefox running on Red Hat EL 5, on a two-CPU 64 bit Intel server. Memory segmentation fault is repeatable when the onchange attribute is used in an input element to trigger the javascript submit function. Sometimes this step can be repeated once or two before it will trigger the crash. The firebug console briefly displays two error messages related to "context" and "out of memory" before crashing. From the command line, run in safe mode, "./run-mozilla.sh: line 131: 10929 Segmentation fault "$prog" ${1+"$@"}" is displayed.
alan: i doubt it. get your own stack trace and file your own bug.
Any news with my bug?
This bug was reported using a version of Firefox that security and stability updates are no longer provided for. All users are strongly encouraged to upgrade to Firefox 3 by selecting 'Check for Updates' in the Help menu or by going to http://www.mozilla.com/en-US/firefox/firefox.html If you can no longer reproduce this bug using the latest Firefox 3.0.x version, please change the status of this bug to 'RESOLVED' 'WORKSFORME'. If you can still reproduce this bug, please provide additional details to help resolve this issue.
Resolving as WORKSFORME. If the issue appears in Firefox 3.5, we will reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: