Closed Bug 266574 Opened 20 years ago Closed 19 years ago

reproducible segmentation fault while accessing a web site

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: flo, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041026 Firefox/0.10.1 (Debian package  0.10.1+1.0PR-4)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041026 Firefox/0.10.1 (Debian package  0.10.1+1.0PR-4)

I noticed a reproducible bug in Mozilla Firefox. My version is Mozilla Firefox
0.10.1 from current Debian GNU/Linux Sid. Firefox creates a segmentation
violation while loading a website. See steps to reproduce.

Reproducible: Always
Steps to Reproduce:
1. Go to http://www.google.de/
2. Search for "UUnet Deutschland GmbH"
3. Visit the first result and wait till page is loaded
4. Click the back button
5. Click the first search result again
Actual Results:  
Segmentation Fault. Firefox killed by Linux Kernel.

Expected Results:  
Load the page.

following lines from strace:

connect(46, {sa_family=AF_FILE, path="/var/run/.nscd_socket"}, 110) = -1 ENOENT
(No such file or directory)
close(46)                               = 0
open("/etc/hosts", O_RDONLY)            = 46
fcntl64(46, F_GETFD)                    = 0
fcntl64(46, F_SETFD, FD_CLOEXEC)        = 0
fstat64(46, {st_mode=S_IFREG|0644, st_size=332, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb3087000
read(46, "127.0.0.1\tlocalhost\n192.168.1.10"..., 4096) = 332
read(46, "", 4096)                      = 0
close(46)                               = 0
munmap(0xb3087000, 4096)                = 0
pipe([46, 47])                          = 0
gettimeofday({1099006068, 209121}, NULL) = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
gettimeofday({1099006068, 222964}, NULL) = 0
rt_sigaction(SIGILL, {0xb3565430, [ILL], SA_RESTART}, {0x8055eb0, [ILL],
SA_RESTART}, 8) = 0
rt_sigaction(SIGILL, {0x8055eb0, [ILL], SA_RESTART}, {0xb3565430, [ILL],
SA_RESTART}, 8) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
unlink("/home/flo/.mozilla/firefox/default.bkm/lock") = 0
rt_sigaction(SIGSEGV, {SIG_DFL}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [SEGV], NULL, 8) = 0
tgkill(7525, 7525, SIGSEGV)             = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---  
+++ killed by SIGSEGV +++


(Mail me if you need complete strace logfile)
wfm, Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041003 Firefox/0.10.1
works with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041026
Firefox/1.0RC1 also.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.