602905 - Plug in Jar Crashes when using Zynga Poker, program will not load then freezes

Status: RESOLVED INCOMPLETE

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

Description

[Lee Chikafsky]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.13) Gecko/20100914 Firefox/3.5.13 ( .NET CLR 3.5.30729; .NET4.0C) PBSTB/1.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.13) Gecko/20100914 Firefox/3.5.13 ( .NET CLR 3.5.30729; .NET4.0C) PBSTB/1.2

When using Zynga Poker, whether direct load or linked from another Zynga game, game does not load, computer freezes, need to use Task Manager to close window upon which Firefox tells you Plug In Container crashed and looks for solution. No solution.  This occurs in newest Upgrade of Firefox.  Gryillda on Spark chat box suggested to downgrade to 3.5 and this totally eliminated issue.  This only happened with the Zynga poker game.  I have downgrade so I can not replicate issue

Reproducible: Always

Steps to Reproduce:
1. From any game in Zynga use Poker Game link or direct load Poker
2. Slowly load program Zynga Poker then freezes
3. 
Actual Results:  
Computer inoperative, frozen.


Expected Results:  
Load program within reasonable time, minute or two

Gyrillda asks me to make this report, was advised to downgrade to 3.5 and given link.  Problem no longer appeared.

Comment 1

[Lee Chikafsky]

I communicated with Zynga to report this issue, they said they were working on it.  For reference, this occurs in Google Chrome current issue and IE 7 & 8.  It was good to know 3.5 dissolved this issue in Firefox, since this is my primary browser.

Comment 2

[timeless]

https://developer.mozilla.org/En/How_to_get_a_stacktrace_with_WinDbg
(32bit windbg, please)

when it gets stuck, debug>break and use:
!analyze -v -hang

i'm assuming this is flash and not java, but please correct me if i'm wrong.

Comment 3

[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.