Closed Bug 596956 Opened 14 years ago Closed 14 years ago

New Adobe Flash Player 64-bit plugin does not work on Minefield 64-bit

Categories

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

x86_64
Windows 7
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: nicholas.65, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; Win64; x64; en-US; rv:1.9.3a5pre) Gecko/20100514 Minefield/3.7a5pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; Win64; x64; en-US; rv:1.9.3a5pre) Gecko/20100514 Minefield/3.7a5pre

There is a new release of Adobe Flash Player plugin for 64-bit browsers that popped up quite recently. I have been trying to use the plugin for a few hours by testing it on sites like e.g Youtube.com , Facebook.com and many more but all have either caused crashes to the plugin-container or just won't load and leave the browser laggy.

Reproducible: Always

Steps to Reproduce:
1.Install the version 3.7 of Minefield(64-bit) from www.mozilla-x86-64.com/
2.Install the new Adobe Flash Plugin from Adobe http://labs.adobe.com/technologies/flashplayer10/
3.Try opening sites that use Adobe plugin like Youtube.com or Facebook.com
Actual Results:  
It would either crash or not start at all

Expected Results:  
It should have opened the application just like it would on Firefox 32-bit
Do you see the plugin in about:plugins ?
Please provide a crash ID https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report
Try 64bit version of http://nightly.mozilla.org/ version.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Component: Extension Compatibility → Flash (Adobe)
Product: Firefox → Plugins
QA Contact: extension.compatibility → adobe-flash
Version: unspecified → 10.x
Version and milestone values are being reset to defaults as part of product refactoring.
Version: 10.x → unspecified
Product: External Software Affecting Firefox → External Software Affecting Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.