Take the 2-minute tour ×

We have an issue were the server session associated with a Flex client times out when the browse file dialog is open for a time longer then the configured session timeout. It seems that on some players, the playback is stopped when browse or download on a FileReference is executing. This also causes remote calls to be blocked and hence our manual keep-alive messages are not sent to the server, resulting in a session timeout.

I searched for some info on this in the docs and found a notice of it, but it does not explicitly list the players it does (not) work. Would anyone know were I could find a complete list?

PS: here are the links that mention this behavior:

While calls to the FileReference.browse(), FileReferenceList.browse(), or FileReference.download() method are executing, most players will continue SWF file playback.

While calls to the FileReference.browse(), FileReferenceList.browse(), or FileReference.download() methods are executing, SWF file playback pauses in stand-alone and external versions of Flash Player and in AIR for Linux and Mac OS X 10.1 and earlier

Anyone knows what is meant with an "external Flash Player"?

PPS: we tested this on Linux (10.0.x and 10.1.x) in Firefox where it seems to stop playback and on Windows (10.0.x) in IE where playback seems to continue.

share|improve this question
add comment

1 Answer

Nothing you can do unfortunately, it's a blocking call, and Player shares resources (incl threads) across multiple instances of the AVM when it can, to use less memory. Chrome, Webkit 2, and FF4 (3.7?) should be OK because they isolate the plugins in separate process spaces, and Player doesn't get a chance to do that. Unfortunately because it's blocking, Chrome will popup a dialog complaining that "a script is taking too long to execute" if you take your sweet time selecting the file :(

github.com/Adobe/FlashPlayer sure would be nice, innit? :-)

share|improve this answer
add comment

Your Answer


