560094 - Adobe flash plugin crashes on opening Adobe's test page in Firefox. [@ 0x7f2c664d3063]

Status: RESOLVED INCOMPLETE

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

Description

[bugzilla]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.3a5pre) Gecko/20100417 Minefield/3.7a5pre
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.3a5pre) Gecko/20100417 Minefield/3.7a5pre

Using the alpha 64-bit flash player available at
http://labs.adobe.com/technologies/flashplayer10/64bit.html version 10.0.45.2 and playing the sample at http://www.adobe.com/software/flash/about/ Firefox reports flash crash, every time.  Reloading the page repeats the result. Many other pages with flash content act in same way.

System is AMD64 with Debian Lenny, all updates applied.


Reproducible: Always

Steps to Reproduce:
1. Open Firefox
2. Go to this page
3. Read the messsage
Actual Results:  
Flash reports crash and invites page reload.

Expected Results:  
Flash displays content.

Comment 1

[timeless]

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

note that we have not shipped a 64bit browser, and we don't currently support mixing 64bit plugins w/ 32bit browsers or vice versa.

In theory our 32bit browser should fail to load your 64bit plugin, crashing w/ that pair probably requires nspluginwrapper which is a third party (buggy) plugin.

Comment 2

[bugzilla]

(In reply to comment #1)
> https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report
> 
> note that we have not shipped a 64bit browser, and we don't currently support
> mixing 64bit plugins w/ 32bit browsers or vice versa.
> 
> In theory our 32bit browser should fail to load your 64bit plugin, crashing w/
> that pair probably requires nspluginwrapper which is a third party (buggy)
> plugin.

This crash was using the 64-bit plugin in the 64-bit browser as the report above states.  nspluginwrapper doesn't work.  Anyway, the crash report reference is http://crash-stats.mozilla.com/report/index/bp-fb804d3c-b315-4950-8cf2-a73392100418 in the hope it helps.

Comment 3

[timeless]

Signature	@0x7f2c664d3063
UUID	fb804d3c-b315-4950-8cf2-a73392100418
Process Type	plugin Version: Filename: libflashplayer.so
Time 	2010-04-18 15:45:32.222599
Uptime	1
Product	Firefox
Version	3.7a5pre
Build ID	20100418030600
Branch	1.9.3
OS	Linux
OS Version	0.0.0 Linux 2.6.26-2-amd64 #1 SMP Tue Mar 9 22:29:32 UTC 2010 x86_64
CPU	amd64
CPU Info	family 15 model 7 stepping 10
Crash Reason	SIGILL
Crash Address	0x7f2c664d3063
User Comments	
Processor Notes 	No proper signature could be created because no good data for the crashing thread (1) was found
Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 		@0x7f2c664d3063 	

Show/hide other threads
Thread 0
Frame 	Module 	Signature [Expand] 	Source
0 	libc-2.7.so 	libc-2.7.so@0xcc259 	
Thread 2
Frame 	Module 	Signature [Expand] 	Source
0 	libpthread-2.7.so 	libpthread-2.7.so@0xad29 	

Filename 	Version 	Debug Identifier 	Debug Filename
libflashplayer.so 		D708CF1409A7A3DE15F591C53914549B0 	libflashplayer.so

Ted: any idea why we don't have a happy stack trace?

Comment 4

[Paul Betlem]

Hi,

The 64-bit alpha version of the Flash Player for Linux is fairly dated. We have a much more mature version in the works that we'll make available once its ready to be formally beta-tested. As a result, I wouldn't spend a lot of time filing bugs for the Alpha version given its age and that the new version has undergone many long hours of improvements.

Comment 5

[(not currently active) Ted Mielczarek]

(In reply to comment #3)
> Ted: any idea why we don't have a happy stack trace?

It's a 64-bit build, which doesn't have a frame pointer, and we don't have symbols for that frame, so we can't walk past it.

Comment 6

[bugzilla]

Is there any idea when the referred-to beta might see the light of day?

Comment 7

[Benjamin Smedberg]

I'm closing a lot of bugs which are filed as Adobe Flash bugs which are either irrelevant, not actionable, or not serious enough to track in the Mozilla bug tracker. For the most part, Flash bugs should be filed in Adobe bugbase, and we'll only track a few highly-critical issues in the Mozilla tracker.

Comment 8

[BMO Automation]

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