Closed Bug 187966 Opened 23 years ago Closed 22 years ago

crash when going to above url and scrolling

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: aldug, Assigned: asa)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202 I'm using the rh8 xft mozilla-1.2.1 rpms on redhat 8.0 and if I go to the above URL in mozilla and scroll it either crashes or hangs mozilla depending on how you scroll. I tried running it through gdb and pressed control-c when mozilla hung and did a backtrace. Not sure how useful this is: (gdb) bt #0 0x42028d69 in sigsuspend () from /lib/i686/libc.so.6 #1 0x4020e108 in __pthread_wait_for_restart_signal () from /lib/i686/libpthread.so.0 #2 0x4020b04b in pthread_cond_wait () from /lib/i686/libpthread.so.0 #3 0x401f4aa5 in PR_WaitCondVar () from /usr/lib/libnspr4.so #4 0x401878a4 in nsThreadPool::GetRequest () from /usr/lib/libxpcom.so #5 0x40187fe9 in nsThreadPoolRunnable::Run () from /usr/lib/libxpcom.so #6 0x40186a93 in nsThread::Main () from /usr/lib/libxpcom.so #7 0x401f97f8 in _pt_root () from /usr/lib/libnspr4.so #8 0x4020c941 in pthread_start_thread () from /lib/i686/libpthread.so.0 #9 0x4020ca45 in pthread_start_thread_event () from /lib/i686/libpthread.so.0 (gdb) quit Reproducible: Always Steps to Reproduce: 1.) go to http://www.gnome.org/~aldug/gnome2/files/nautilus-rpm_build_error.txt 2.) Scroll using mousewheel or sidebar Actual Results: Mozilla hangs or crashes Expected Results: page should scroll
couldn't repro this one but i have a very similar problem, also on RH8, reported in bug 187274
Go to rpmfind.net Type in mozilla Download the latest Redhat Rawhide RPMs mozilla-1.4b-1.i386.rpm mozilla-nss-1.4b-1.i386.rpm mozilla-mail-1.4b-1.i386.rpm mozilla-psm-1.4b-1.i386.rpm mozilla-nspr-1.4b-1.i386.rpm sudo rpm -Uvh moxilla* problem solved
Reporter: Can you reproduce this bug with a recent build of Mozilla (for example, 1.4rc3)? If so, then please comment again with details. If not, then please resolve this bug as WORKSFORME. Thanks.
Reporter, if you see this problem in a recent build of Mozilla, feel free to return and reopen the bug. RESOLVING WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.