Closed Bug 120893 Opened 23 years ago Closed 16 years ago

Browser hangs hard, often on scrolling, other screen updates

Categories

(Core :: Layout, defect, P1)

x86
Windows 95
defect

Tracking

()

RESOLVED WORKSFORME
Future

People

(Reporter: ess, Unassigned)

References

Details

(Keywords: crash)

Attachments

(1 file)

Particularly when scrolling with the scroll wheel, I find that Mozilla hangs hard.  The computer 
has to be rebooted -- [CTRL][ALT][DEL] is the only keystroke to which Windows will respond (the 
mouse pointer disappears).  While opening a new tab or sometimes just loading a page will provoke 
this kind of a freeze, giving the mouse wheel a good workout, perhaps especially while the page is 
still loading, is a really good way to provoke this freeze.

Build Bar forum participants on 
MozillaZine report seeing similar freezing:

...in 
Win2000
http://www.mozillazine.org/talkback/read.php?f=4&i=622&t=606

...in 
Win98 SE
http://www.mozillazine.org/talkback/read.php?f=4&i=642&t=606

...in 
builds as recent as 
Thursday's:
http://www.mozillazine.org/talkback/read.php?f=4&i=656&t=606

Mozilla 
freezes typically in the midst of redrawing the screen (the bottom line of the screen will be 
repeated and/or broken up).  The moust pointer vanishes.  Windows stops responding to 
keystrokes.  You must reboot.

Pre-Christmas nightly builds were behaving well.  Around New 
Year's, they became wildly unstable for me, hanging often.  They have improved since then, but the 
problem does exist.  Pre-Christmas, I can't remember this ever happening -- Mozilla hasn't hung or 
crashed hard enough to force me to reboot in ages.
Build 2002011103 does this fairly reliably.  Builds from January 4th and January 7th were, as I 
recall, even worse.
Adding crash keyword.  Please remove it if I've guessed incorrectly about what it's for.
Keywords: crash
Yes, I see this as well. It doesn't matter how the page is scrolled, page
up/down or scrollbars seem to cause a system hang.

I've had this with every build after 0.9.7 I tried, but I'm not sure how recent
the first one was.

The most recent build that I tried was 2002012505. Same problem.

I also get a crash next time I start the browser up. This isn't picked up by
Talkback (I don't think it has a chance to start up, if you start with console
you only see the first two lines)

The standard Windows crash box says:

MOZILLA caused an invalid page fault in
module MSVCRT.DLL at 014f:7800272e.
Registers:
EAX=ffffffff CS=014f EIP=7800272e EFLGS=00010246
EBX=00000000 SS=0157 ESP=0064f348 EBP=0064f378
ECX=00000000 DS=0157 ESI=0064f368 FS=0e9f
EDX=00000001 ES=0157 EDI=00820ba0 GS=0000
Bytes at CS:EIP:
8b 01 ba ff fe fe 7e 03 d0 83 f0 ff 33 c2 83 c1 
Stack dump:
60febb45 00000000 00820ba0 6100c889 00000000 ffffffff 00000001 0081de50 61028094
00000000 ffffffff 00000001 0064f3a0 6100ce5b 00000000 61027dac

I'm on Windows 95, and I always get talkback ZIP builds (although my 0.9.7
fallback build is SVG)

It was suggested on #mozillazine that deleting localstore.rdf might help. It didn't.
could 101055, 123196 or 117724 be related?

This *still* happens with 0.9.8.

Yes, this bug seems strongly interconnected with 117724 . Can everybody 
affected here try to reproduce the the test case there. That bug has quite
similar crashes during scrolling, also appeared between 0.9.6 and 0.9.7, still 
is unconfirmed because it triggers only on particular PC hardware (for me it's 
a SIS-730S based mainboard) but all Microsoft OS. It would be great to find 
out, what hardware is affected. And in 0.9.8+ the problem is still present.
*** Bug 117724 has been marked as a duplicate of this bug. ***
I think this is an interaction with the hardware acceleration somehow.

I have an ATI Mach 64 card, and with acceleration set to full, the problem is there.

If I turn the acceleration down to "Basic Accelerator Functions" or "None" the
problem goes away.

When the card is in the levels of acceleration without a crash, scrolling is
noticably worse than the levels with a crash - suggesting it is the scrolling
acceleration that is doing it.

I suggest other people with this problem try the following steps:

1: Right-click on your desktop, and select "Properties" to bring up display settings
2: Select the "Settings" tab
3: Press the "Advanced Properties" button
4: Select the "Performance" tab
5: Drag the slider so basic or no acceleration is selected (first two levels)
6: Press "OK" and "Close" to confirm
7: Agree to restart when asked
8: Try to crash

I have also found that if I get the crashes on startup which follow this bug
being triggered, deleting component.reg fixes it.
Yes, switching video optimizations down to "basic" allows Mozilla to run 
properly. Though this also breaks DirectDraw and Direct3D. Games and Movie-
Players failed to work after the switch. Therefore this is not a viable 
solution to the problem.

To sum up Hardware which seems to be affected by this bug till now:

- Mainboard based on SIS-730S with a built-in SIS-300 graphics chip (me)

- ATI Mach 64 (kirun)

- Thinkpad 380Z having a NeoMagic MagicMedia256AV (NM2200) graphics chip (some 
guy in the mozillazine forum)

This is definitely not a hardware-manufacturer specific problem. I guess the 
problem lies in the code section interfacing with the win32 GDI layer. It uses 
it somehow (probably to gain some speed) which is tolerated by a huge part of 
hardware&devicedrivers out there but causes problems on a small fraction of 
hardware&devicedrivers.

I don't know what fraction of Mozilla is developped in-house but companies tend 
to buy their hardware often from just a very few sources. Therefore it is quite 
possible that most of developers and QA never have this specific problem.
No problems for me: Windows XP build 2002021303
NVIDIA GeForce 2
Microsoft Intellimouse Explorer
Confirming bug per earlier comments, to get it on the radar.

Reporter:  Can you use a Talkback-enabled build and send in a crash report?  
That will help out a lot in triaging this bug appropriately.
Status: UNCONFIRMED → NEW
Component: Browser-General → Layout
Ever confirmed: true
Reducing severity to critical (I'm not sure if this should block 0.9.9 release).
Assignee: asa → attinasi
Severity: blocker → critical
QA Contact: doronr → petersen
I thought this is a dup of a known issue with some cards. Guess there is need
for more testing, maybe a recent optimization on imagelib?
You can't generate a talkback for this bug - it locks up your whole system, not
just mozilla. Talkback doesn't trigger.
As talkback doesn't work for this case I've got another offer: I strongly hope 
that old nightly binaries are archived somewhere (maybe on CD-R). If I can get 
access to win32-binaries of all nightly builds between 0.9.6 and 0.9.7 I'm 
willing to take some time and find out the very first nightly that crashes the 
machine. Then we need to time-travel to that particular day/hour using CVS to 
find the checkin that might have caused the problem.

One strange sidenote through: though my machine appears to completely frozen, it 
remains pingable over the net. This in fact means, that some parts of the OS are 
still running and it could be possible to gather further informations using the 
Compuware Soft-ICE kernel-level-debugger controlled through a terminal hanging 
on a serial port. But as Soft-ICE is REALLY expensive, I'd suggest this only as 
a last resort.

_basic: could you tell us the bug #'s of the similar bug's you're talking about?
Priority: -- → P1
Target Milestone: --- → Future
This still happens with RC2. I updated my drivers to the latest ones on the ATi
site and the problem remains. It can take a while for the problem to surface.

One thing I have noticed is my 0.9.7 SVG build (2002010204) does not have this
bug on scrolling pages. It does, however, have the bug scrolling some other
things (such as dropdown lists or the list of stored cookies).

Was there some code interacting with acceleration that was introduced in two
parts somehow? Widgets first, pages later? 

I appreciate it's hard for any developers to reproduce this, as they don't have
the right kind of card. If running some specially prepared build (with logs etc)
would help, then I'll do that.
->dcone.
Assignee: attinasi → dcone
I am experiencing this bug with 1.1 branch build 2002081204, and some other 1.1
builds from about a week before that.  Scrolling on certain pages locks the
machine completely.  Not even ctrl-alt-del restarts the computer; I have to use
the harware reset switch.

The affected system is running Windows 2000 and has an ATI Radeon 7000-based
video card.  The problems began immediately after upgrading the video drivers
from version 5.13.01.6094 to version 5.13.01.6118 from the ATI web site.

The bug is triggered reliably on certain pages, including:
<http://www.linux.org.uk/cgi-bin/portaloo?addall=maths>

I'm willing to run test binaries or other diagnostics to help fix this bug.  In
the near future I will try downgrading the video drivers and/or disabling
acceleration to test the affect.
(Cont'd from comment #17)  The bug no longer occurs after setting the
acceleration to "Basic only" in the Troubleshooting section of the Display settings.
I believe I am experiencing this bug with 1.0, but with other interesting
twists.   I am running Windows 2000 with an ATI Radeon 8500 video card.  When my
system hangs, the mouse cursor freezes, the keyboard becomes totally
unresponsive (no CTRL+ALT+DEL response, and LED lights are frozen), but my
computer continues to move video from my capture card and sound audio.  It
appears that a few web pages trigger the bug quite easily, while others don't
seem to trigger it at all.  The pages that trigger the bug most easily are valid
HTML/XHTML, so I'm not sure what to think there.  I can trigger the bug by
scrolling quickly (and sometimes slowly) with the mouse wheel, but not with the
keyboard arrow keys or page up/down keys.  I can also trigger the bug in Opera,
but not in Internet Explorer.  As suggested by others, I disabled video
acceleration and so far I can not reproduce the bug (in Mozilla...haven't tried
Opera yet).  I upgraded my video card drivers and installed Win2k SP3 several
days ago, and I believe my problems with the bug started about the same time.
From the Gimp Win32 page (http://www.gimp.org/~tml/gimp/win32/)

Many people with ATI Rage Pro cards have complained about display errors. It
seems that this is a known problem with the drivers for these cards, and can be
worked around by setting DEVBMP=0 in the [display] section of the Windows
system.ini file, like this:

[display] 
DEVBMP=0 

This also appears to fix the scroll crash for me.
(cont'd from comment #17) Reverting to the Win2K Radeon driver version
5.13.01.6071 fixed the crash on this machine.  The DEVBMP line mentioned in
comment #20 did not work with this machine.
The bug caused me trouble also.

Steps to reproduce (100% reproduceable in my environment):
1) Have a Windows (Windows 2000 sp3 in my case) machine with an ATI video card 
(mine: Radeon 64 DDR VIVO) having driver 5.13.01.6118.
2) Start Mozilla and go to <http://www.linux.org.uk/cgi-bin/portaloo?
addall=maths>
3) Open new tab (Ctrl-T)
4) Return to the first tab
5) Try to scroll down
6) Machine freezes, only mouse cursor can be moved. NumLock LED frozen. Ctrl-
Alt-Del gets ignored.
7) Mouse cursor also freeze after a while
8) Other application seem to work at background, but screen picture is frozen.

Workaround (worked in my case):
remove the 5.13.01.6118 driver and install 5.13.01.6071

Not very sure what software to blame, but I have filed bug report on 
support.ati.com.
Does anyone seeing this problem not have an ATI card?  There are a couple of
other bugs about crashes with ATI video cards.
In reply to comment #23 (are non-ATI cards affected?):

Yes.  See for example comment #8 and comment #9.  Affect video cards include
SIS, nVidia, NeoMagic.
ATI has released new driver version 5.13.01.6166 (a.k.a. CATALYST 02.3).
In the Release Notes, they explicitly claim that "Hanging issues with Mozilla
browser" are resolved.
I tried this driver with my previous test case and it worked OK.
No more hangs using Mozilla for 3 days.
Depends on: 101055
Attached image Screenshot of #120893 (deleted) —
I've reported this as #158143 previously, but it seems that most of the activity
is at this bug number, so I'll report some new information here.

I have some anecdotal evidence that using the Microsoft truetype core fonts
(Debian's msttcorefonts package) makes the problem much more likely.  I re-enabled
them recently on the AMD Duron mentioned below and the problem began recurring 
much more frequently.

I've seen this on the following machines:

 - Toshiba Satellite S303 (PIII) with NVidia GeForce2Go + Debian woody
 - Generic AMD Duron with NVidia GeForce II MX + Debian woody
 - Generic Celeron with 3dfx Voodoo 3 + Debian woody
 - Generic AMD T-bird with NVidia GeForce II MX + Debian woody

These two URLs provide 100% repeatability of the bug on my machines, which are
available for remote debugging if needed:

http://www.pcchips.com.tw/BIOS.html
http://story.news.yahoo.com/news?tmpl=story&u=/nm/20021105/people_nm/people_kidman_dc_1

On all four systems, a strip of the bottom window is duplicated, often trimming
a line of text in half in the process.  I've attached a screenshot of the
result.

Here are stack dumps of two instances of the problem:

(gdb) btt

Thread 9 (Thread 114696 (LWP 25653)):
#0  0x4027bc92 in sigsuspend () from /lib/libc.so.6
#1  0x4020a6dd in __pthread_wait_for_restart_signal ()
   from /lib/libpthread.so.0
#2  0x40207149 in pthread_cond_wait () from /lib/libpthread.so.0
#3  0x401f0ef2 in PR_WaitCondVar () from /usr/lib/libnspr4.so
#4  0x4017f8c5 in nsThreadPool::GetRequest () from /usr/lib/libxpcom.so
#5  0x40180114 in nsThreadPoolRunnable::Run () from /usr/lib/libxpcom.so
#6  0x4017eb3e in nsThread::Main () from /usr/lib/libxpcom.so
#7  0x401f5c6d in PR_Select () from /usr/lib/libnspr4.so
#8  0x40208048 in pthread_start_thread () from /lib/libpthread.so.0
#9  0x4020808e in pthread_start_thread_event () from /lib/libpthread.so.0

Thread 5 (Thread 49156 (LWP 25649)):
#0  0x402f0671 in nanosleep () from /lib/libc.so.6
#1  0x4020a809 in __pthread_timedsuspend_new () from /lib/libpthread.so.0
#2  0x40207397 in pthread_cond_timedwait_relative () from /lib/libpthread.so.0
#3  0x40207524 in pthread_cond_timedwait () from /lib/libpthread.so.0
#4  0x401f0cfc in PR_Unlock () from /usr/lib/libnspr4.so
#5  0x401f0f06 in PR_WaitCondVar () from /usr/lib/libnspr4.so
#6  0x40181cb6 in TimerThread::Run () from /usr/lib/libxpcom.so
#7  0x4017eb3e in nsThread::Main () from /usr/lib/libxpcom.so
#8  0x401f5c6d in PR_Select () from /usr/lib/libnspr4.so
#9  0x40208048 in pthread_start_thread () from /lib/libpthread.so.0
#10 0x4020808e in pthread_start_thread_event () from /lib/libpthread.so.0

Thread 4 (Thread 32771 (LWP 25637)):
#0  0x4027bc92 in sigsuspend () from /lib/libc.so.6
#1  0x4020a6dd in __pthread_wait_for_restart_signal ()
   from /lib/libpthread.so.0
#2  0x40207149 in pthread_cond_wait () from /lib/libpthread.so.0
#3  0x401f0ef2 in PR_WaitCondVar () from /usr/lib/libnspr4.so
#4  0x406d64b3 in NSGetModule () from /usr/lib/mozilla/components/libnecko.so
#5  0x406d5f5c in NSGetModule () from /usr/lib/mozilla/components/libnecko.so
#6  0x4017eb3e in nsThread::Main () from /usr/lib/libxpcom.so
#7  0x401f5c6d in PR_Select () from /usr/lib/libnspr4.so
#8  0x40208048 in pthread_start_thread () from /lib/libpthread.so.0
#9  0x4020808e in pthread_start_thread_event () from /lib/libpthread.so.0

Thread 3 (Thread 16386 (LWP 25636)):
#0  0x4031240c in poll () from /lib/libc.so.6
#1  0x401f4ae5 in PR_OpenDir () from /usr/lib/libnspr4.so
#2  0x401f4c14 in PR_Poll () from /usr/lib/libnspr4.so
#3  0x406cc4b5 in NSGetModule () from /usr/lib/mozilla/components/libnecko.so
#4  0x4017eb3e in nsThread::Main () from /usr/lib/libxpcom.so
#5  0x401f5c6d in PR_Select () from /usr/lib/libnspr4.so
#6  0x40208048 in pthread_start_thread () from /lib/libpthread.so.0
#7  0x4020808e in pthread_start_thread_event () from /lib/libpthread.so.0

Thread 2 (Thread 32769 (LWP 25635)):
#0  0x4031240c in poll () from /lib/libc.so.6
#1  0x40207d82 in __pthread_manager () from /lib/libpthread.so.0
#2  0x40207f4a in __pthread_manager_event () from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 25633)):
#0  0x40313c5e in select () from /lib/libc.so.6
#1  0x405b3cbc in _XlcPublicMethods () from /usr/X11R6/lib/libX11.so.6
#2  0x4052b1ea in _XRead () from /usr/X11R6/lib/libX11.so.6
#3  0x4052bbf3 in _XReply () from /usr/X11R6/lib/libX11.so.6
#4  0x405278b7 in XSync () from /usr/X11R6/lib/libX11.so.6
#5  0x40828150 in gdk_superwin_scroll () from /usr/lib/libgtksuperwin.so
---Type <return> to continue, or q <return> to quit---
#6  0x407fe523 in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#7  0x412d8910 in NSGetModule () from /usr/lib/mozilla/components/libgkview.so
#8  0x412d8350 in NSGetModule () from /usr/lib/mozilla/components/libgkview.so
#9  0x412d86ed in NSGetModule () from /usr/lib/mozilla/components/libgkview.so
#10 0x40a90e4a in NSGetModule ()
   from /usr/lib/mozilla/components/libgkcontent.so
#11 0x40a91bc6 in NSGetModule ()
   from /usr/lib/mozilla/components/libgkcontent.so
#12 0x4112e87f in NSGetModule ()
   from /usr/lib/mozilla/components/libgklayout.so
#13 0x4112e607 in NSGetModule ()
   from /usr/lib/mozilla/components/libgklayout.so
#14 0x412dd58e in NSGetModule () from /usr/lib/mozilla/components/libgkview.so
#15 0x412d1d58 in NSGetModule () from /usr/lib/mozilla/components/libgkview.so
#16 0x412dcb94 in NSGetModule () from /usr/lib/mozilla/components/libgkview.so
#17 0x412d1843 in NSGetModule () from /usr/lib/mozilla/components/libgkview.so
#18 0x407f922e in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#19 0x407f9120 in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#20 0x407f99d6 in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#21 0x407fd46a in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#22 0x407fd704 in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#23 0x407f34aa in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#24 0x407f320c in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#25 0x404a44d7 in gdk_wm_protocols_filter () from /usr/lib/libgdk-1.2.so.0
#26 0x404d44c8 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#27 0x404d4ad3 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#28 0x404d4c6c in g_main_run () from /usr/lib/libglib-1.2.so.0
#29 0x403f57f7 in gtk_main () from /usr/lib/libgtk-1.2.so.0
#30 0x407eb776 in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#31 0x407ceac8 in NSGetModule ()
   from /usr/lib/mozilla/components/libnsappshell.so
#32 0x08051ee3 in getCountry ()
#33 0x080527ee in main ()
#34 0x4026a9d3 in __libc_start_main () from /lib/libc.so.6
#0  0x4031240c in poll () from /lib/libc.so.6


==============================================================================


Thread 10 (Thread 131081 (LWP 24342)):
#0  0x4027bc92 in sigsuspend () from /lib/libc.so.6
#1  0x4020a6dd in __pthread_wait_for_restart_signal ()
   from /lib/libpthread.so.0
#2  0x40207149 in pthread_cond_wait () from /lib/libpthread.so.0
#3  0x401e1ef2 in PR_WaitCondVar () from /usr/lib/libnspr4.so
#4  0x401708c5 in nsThreadPool::GetRequest () from /usr/lib/libxpcom.so
#5  0x40171114 in nsThreadPoolRunnable::Run () from /usr/lib/libxpcom.so
#6  0x4016fb3e in nsThread::Main () from /usr/lib/libxpcom.so
#7  0x401e6c6d in PR_Select () from /usr/lib/libnspr4.so
#8  0x40208048 in pthread_start_thread () from /lib/libpthread.so.0
#9  0x4020808e in pthread_start_thread_event () from /lib/libpthread.so.0

Thread 5 (Thread 49156 (LWP 24336)):
#0  0x402f0671 in nanosleep () from /lib/libc.so.6
#1  0x4020a809 in __pthread_timedsuspend_new () from /lib/libpthread.so.0
#2  0x40207397 in pthread_cond_timedwait_relative () from /lib/libpthread.so.0
#3  0x40207524 in pthread_cond_timedwait () from /lib/libpthread.so.0
#4  0x401e1cfc in PR_Unlock () from /usr/lib/libnspr4.so
#5  0x401e1f06 in PR_WaitCondVar () from /usr/lib/libnspr4.so
#6  0x40172cb6 in TimerThread::Run () from /usr/lib/libxpcom.so
#7  0x4016fb3e in nsThread::Main () from /usr/lib/libxpcom.so
#8  0x401e6c6d in PR_Select () from /usr/lib/libnspr4.so
#9  0x40208048 in pthread_start_thread () from /lib/libpthread.so.0

Thread 4 (Thread 32771 (LWP 24334)):
#0  0x4027bc92 in sigsuspend () from /lib/libc.so.6
#1  0x4020a6dd in __pthread_wait_for_restart_signal ()
   from /lib/libpthread.so.0
#2  0x40207149 in pthread_cond_wait () from /lib/libpthread.so.0
#3  0x401e1ef2 in PR_WaitCondVar () from /usr/lib/libnspr4.so
#4  0x406d24b3 in NSGetModule () from /usr/lib/mozilla/components/libnecko.so
#5  0x406d1f5c in NSGetModule () from /usr/lib/mozilla/components/libnecko.so
#6  0x4016fb3e in nsThread::Main () from /usr/lib/libxpcom.so
#7  0x401e6c6d in PR_Select () from /usr/lib/libnspr4.so
#8  0x40208048 in pthread_start_thread () from /lib/libpthread.so.0

Thread 3 (Thread 16386 (LWP 24333)):
#0  0x4031240c in poll () from /lib/libc.so.6
#1  0x401e5ae5 in PR_OpenDir () from /usr/lib/libnspr4.so
#2  0x401e5c14 in PR_Poll () from /usr/lib/libnspr4.so
#3  0x406c84b5 in NSGetModule () from /usr/lib/mozilla/components/libnecko.so
#4  0x4016fb3e in nsThread::Main () from /usr/lib/libxpcom.so
#5  0x401e6c6d in PR_Select () from /usr/lib/libnspr4.so
#6  0x40208048 in pthread_start_thread () from /lib/libpthread.so.0

Thread 2 (Thread 32769 (LWP 24332)):
#0  0x4031240c in poll () from /lib/libc.so.6
#1  0x40207d82 in __pthread_manager () from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 24280)):
#0  0x40313c5e in select () from /lib/libc.so.6
#1  0x405b3cbc in _XlcPublicMethods () from /usr/X11R6/lib/libX11.so.6
#2  0x4052b1ea in _XRead () from /usr/X11R6/lib/libX11.so.6
#3  0x4052bbf3 in _XReply () from /usr/X11R6/lib/libX11.so.6
#4  0x405278b7 in XSync () from /usr/X11R6/lib/libX11.so.6
#5  0x40815150 in gdk_superwin_scroll () from /usr/lib/libgtksuperwin.so
#6  0x407fa523 in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#7  0x412d7910 in ?? ()
#8  0x412d7350 in ?? ()
---Type <return> to continue, or q <return> to quit---
#9  0x412d76ed in ?? ()
#10 0x40a8fe4a in NSGetModule ()
   from /usr/lib/mozilla/components/libgkcontent.so
#11 0x40a90bc6 in NSGetModule ()
   from /usr/lib/mozilla/components/libgkcontent.so
#12 0x4112d87f in ?? ()
#13 0x4112d607 in ?? ()
#14 0x412dc58e in ?? ()
#15 0x412d0d58 in ?? ()
#16 0x412dbb94 in ?? ()
#17 0x412d0843 in ?? ()
#18 0x407f522e in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#19 0x407f5120 in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#20 0x407f59d6 in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#21 0x407f946a in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#22 0x407f9704 in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#23 0x407ef4aa in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#24 0x407ef20c in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#25 0x404a44d7 in gdk_wm_protocols_filter () from /usr/lib/libgdk-1.2.so.0
#26 0x404d44c8 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#27 0x404d4ad3 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#28 0x404d4c6c in g_main_run () from /usr/lib/libglib-1.2.so.0
#29 0x403f57f7 in gtk_main () from /usr/lib/libgtk-1.2.so.0
#30 0x407e7776 in NSGetModule ()
   from /usr/lib/mozilla/components/libwidget_gtk.so
#31 0x407caac8 in NSGetModule ()
   from /usr/lib/mozilla/components/libnsappshell.so
#32 0x08051ee3 in getCountry ()
#33 0x080527ee in main ()
#34 0x4026a9d3 in __libc_start_main () from /lib/libc.so.6

*** Bug 161766 has been marked as a duplicate of this bug. ***
WFM on 1.08/03 Trunk with nVidia GeForce2 MX/MX400.
WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-CA; rv:1.0.2) Gecko/20021120
Netscape/7.01 with NVIDIA GeForce 256.
Can anybody still reproduce this bug?
I think this is what I'm having on Debian stable (including moz 1.4).
Happens on a variety of websites.
This is confirmed a problem on OS X 10.3.9 also.  Release 1.0.6 is unusable to
me -- I cannot browse more than a few minutes before the entire system hangs due
to this process eating all of the CPU and not returning it!  I have to usually
kill the runaway process.

i would say this was a blocker, even though it compils and runs -- if your
system is going to die by running this...
do you see this problem when running version 3?
Assignee: dcone → nobody
QA Contact: chrispetersen → layout
Whiteboard: closeme 2008-12-28
Please try Firefox 3:  http://www.mozilla.com/firefox/
File a new bug if the problem remains.  Thanks for your report.

-> WORKSFORME
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Whiteboard: closeme 2008-12-28
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: