Plugin handler for flash "detects" crash when debugging.

RESOLVED WORKSFORME

Status

External Software Affecting Firefox
Flash (Adobe)
RESOLVED WORKSFORME
7 years ago
2 years ago

People

(Reporter: bugzilla, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)

Because plugins are deemed crashed based on a timer, if I have a break-point in my flex code (Flash Builder 4) and am inspecting variables (or other general debugging stuff), FF detects the plugin as crashed, thereby ending my debugging session.


Reproducible: Always

Steps to Reproduce:
1. Create some flex code
2. Add breakpoint
3. Debug
4. Wait 30 seconds

Actual Results:  
Debug session ended. Flash player/Application closed

Expected Results:  
Should be able to continue debugging without it FF killing my debug session.

Seems the plugin handler was rushed a bit. It would be great for us more "advanced" users to 

a) Be able to switch it off somewhere in about:config
b) Be able to set the timeout somewhere in about:config
You can manually set the |dom.ipc.plugins.timeoutSecs| entry in about:config to the number of seconds that you wish to allow waiting.
(Reporter)

Updated

7 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
Resolution: INVALID → WORKSFORME

Comment 2

7 years ago
i think it should be possible for the flash team to change how their plugin works so it doesn't break this...
Component: General → Flash (Adobe)
Product: Firefox → Plugins
QA Contact: general → adobe-flash
Version: unspecified → 10.x

Comment 3

2 years ago
Version and milestone values are being reset to defaults as part of product refactoring.
Version: 10.x → unspecified
You need to log in before you can comment on or make changes to this bug.