flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: different error situation with debugging and non debugging player version
Date Mon, 25 Aug 2014 20:00:32 GMT
Timing is the most common reason for differences.  The release player can
crank through code and hit the server more often or before other
asynchronous data a request depended on was available.

Security is next.  Often folks test debugger versions in a LocalTrusted
sandbox and release version on a Remote sandbox.

Configuration Differences.  Again, if you are testing the release version
on the server vs the debug version locally, some URL or relative path may
not be correct.

Debug-only code  (including expressions in trace statements).

Bugs in the compiler's optimizer.

On 8/25/14 12:30 PM, "mark goldin" <markzolotoy@gmail.com> wrote:

>I am trying to trouble shot an error. The error has something to do with
>server side processing. If I run my app. in the Browser with a debugging
>version of Player then I dont see the error, but non debugging player will
>generate an error. Without going into details about the error why would
>Players act differently?

View raw message