613926 - Firefox crashes in Google image search when scrolling down [@ NPSWF32.dll@0xe3803]

Status: RESOLVED WORKSFORME

(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)

Description

[t8av]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101026 BTRS28059 Firefox/3.6.12 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101026 BTRS28059 Firefox/3.6.12 ( .NET CLR 3.5.30729)

When I use Google image search (the new version, with lots of images in one page), if I scroll down too fast (faster than the images load), firefox crashes.


Reproducible: Always

Steps to Reproduce:
1. Go to Google image search and look for any keyword. For example: http://www.google.com/images?source=imghp&q=flower

2. Scroll down faster than the images load to the page. Probably to reproduce the crash - the faster the better.

Actual Results:  
Firefox crashes

Expected Results:  
Images may load slow, but firefox should not crash.

Comment 1

[t8av]

The problem occurs only sometimes. Maybe only when there are many open tabs already.

If you cannot reproduce the problem - Try to open many tabs with Google image search (scroll down fast for every new tab) until you see the crash.

Comment 2

[Matthias Versen [:Matti]]

Please post a crash ID from about:crashes
https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report

Comment 3

[t8av]

The last crash:

http://crash-stats.mozilla.com/report/index/af817a4f-3a4d-4cca-9224-c55962101122

I will submit more reports when more crashes happen.

Comment 4

[Matthias Versen [:Matti]]

The flash plugin is crashing and you are using an old version of flash.
"NPSWF32.dll 	10.0.2.54"

Please upgrade your flash plugin and try it again.

Comment 5

[timeless]

Signature	NPSWF32.dll@0xe3803
UUID	af817a4f-3a4d-4cca-9224-c55962101122
Time 	2010-11-22 05:05:25.727365
Uptime	19440
Install Age	609372 seconds (1.0 weeks) since version was first installed.
Product	Firefox
Version	3.6.9
Build ID	20100824153629
Branch	1.9.2
OS	Windows NT
OS Version	6.0.6002 Service Pack 2
CPU	x86
CPU Info	GenuineIntel family 6 model 23 stepping 7
Crash Reason	EXCEPTION_ACCESS_VIOLATION_READ
Crash Address	0x0
User Comments	
Processor Notes 	
EMCheckCompatibility	False
Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 	NPSWF32.dll 	NPSWF32.dll@0xe3803 	
1 		@0x6e0068 	
2 	NPSWF32.dll 	NPSWF32.dll@0xbc2d2 	
3 	NPSWF32.dll 	NPSWF32.dll@0xbfdd0 	
4 	NPSWF32.dll 	NPSWF32.dll@0x4242b 	
5 	NPSWF32.dll 	NPSWF32.dll@0x5bfa4 	
6 	NPSWF32.dll 	NPSWF32.dll@0x5bfba 	
7 	NPSWF32.dll 	NPSWF32.dll@0x5bfda 	

Filename 	Version 	Debug Identifier 	Debug Filename
NPSWF32.dll 	10.0.2.54 	E214D1CB28F545C9A386B7554CD5410F1 	NPSWF32.pdb

hopefully this is fixed in a current version of flash. please confirm.

Comment 6

[t8av]

Well, I uninstalled the flash plugin and re-installed it.

When entering Google image search, this time only one tab crashed (stopped responding), not the entire browser, so there was no new crash entry at about:crashes.

Comment 7

[timeless]

for the record, what version of flash are you now using? :)

Comment 8

[t8av]

Tools -> Add-ons -> Plugins -> Shockwave flash 10.1.102.64

Comment 9

[t8av]

Maybe the word "crash" was incorrect. Actually it is extreme slowness which makes the browser unusable. It always happens when I go to Google image search and scroll down. At a certain point the browser suddenly starts to react extremely slow and becomes unusable.

There are no crash reports in about:crashes because the browser did not entirely crash (but was very close to it). It means that I don't know how to send you reports about this when it occurs.

Comment 10

[timeless]

your initial report was a crash. slowness is roughly like hanging, except much better.

you'd need a new bug report.

https://developer.mozilla.org/En/How_to_get_a_stacktrace_with_WinDbg

see the part about hangs.

Comment 11

[t8av]

Well, I uninstalled plugin "Microsoft .NET framework assistant 1.2.1" and so far the problem did not repeat (extreme slowness).

However, one time the browser disappeared. It looks like crash but still the download window was still open and no crash report was in about:crashes.

Comment 12

[timeless]

if the download window was still open, it wasn't a crash, it'd mean something trusted decided you asked it to close a browser window (more or less) .. in theory you could have clicked a js link in window A which opened a window B; you could have closed window A yourself; since window B was opened by a web page, it's allowed to be closed by a web page....

Comment 13

[BMO Automation]

Version and milestone values are being reset to defaults as part of product refactoring.