Skip to main content
R
rootsounds-ihYz70
Participating Frequently
June 24, 2010
Question

Flash 10.1.53.64 - no flashlog.txt logging

  • June 24, 2010
  • 7 replies
  • 39775 views

Configuration:

  • Windows XP SP3 x86
  • FlashDevelop IDE 3.2.1
  • Flex SDK 3.5.0.12683
  • Browsers: Firefox 3.6.4 (with Firebug and Flashbug) and IE8
  • Flash Player Debugger 10.1.53.64

Issue Overview:

Since upgrading from the debug player 10.0.45.2 to the latest 10.1.53.64, I've found that my trace statements are no long written to flashlog.txt from either Firefox or IE. No logs are written, which is a pretty big deal during development.

Consider that it does affect the players in both browsers. I do have mm.cfg configured correctly as per the KB instructions (no change was required, although I did experiment). I am indeed compiling in debug mode. It's not a Flashbug issue as flashlog.txt never gets updated.

Research:

I wasn't able to find much of anything in my searching. There was maybe one blog post with comments suggesting a similar issue with a 10.1RC, but didn't offer up any solutions (I hadn't been developing with the RCs). Also, I couldn't find a relevant entry in the Flash Player bug tracker.

Workaround?

For the time being, I am forced to revert back to 10.0.45.2 which worked immediately. Has anyone else experienced this issue?

    This topic has been closed for replies.

    7 replies

    C
    CharSkin-FyHjjw
    Participant
    August 11, 2010

    Just like to add that I have the same problem. Getting no traces from Flash Player 10.1 in MSIE 8. Had to revert to 10.0 to fix the problem.

    My application is a mix of Flash 8 swf's and Flex 3 swf's. Debugging in Flash Builder works fine and i get traces from the Flex code (not that i really need them). But the Flash 8 swf's don't show any traces. By the way I'm using Service Capture to display the traces.

    K
    Keyston
    Participant
    August 5, 2010

    Just Close PS, i wrote an semi indept blog post about this

    http://ihaveinternet.com/2010/08/05/scriptuiflexserver-and-flashlog-txt/

    And the Bug

    https://bugs.adobe.com/jira/browse/FP-5176

    DavidSalahi
    DavidSalahi
    Known Participant
    August 5, 2010

    Wow, thanks a million for the tip! That was the problem. Exiting Photoshop gets my flashlog.txt logging back along with trace output in Flashbug.

    Thanks again,

    Dave

    E
    Eric Fickes
    Participating Frequently
    August 4, 2010

    I am on OS X and have the same problem with Chrome and Firefox.  FP 10.1.53.64.

    I went so far as to remove the Macromedia folder and reinstall FP 10.1 Debugger and no difference.

    DavidSalahi
    DavidSalahi
    Known Participant
    August 4, 2010

    I'm also failing to get trace output in flashlog.txt. I have the following statements in mm.cfg:

    ErrorReportingEnable=1
    TraceOutputFileEnable=1

    but I get no trace output.

    Curiously, flashlog.txt was modified earlier today, apparently by Photoshop; here's the entire contents of the file:

    Load Bundle at C:\Program Files\Adobe\Adobe Photoshop CS5 (64 Bit)\Plug-ins\Extensions **********Running app: C:\Program Files\Adobe\Adobe Photoshop CS5 (64 Bit)\Plug-ins\Extensions\ScriptUIFlexServer-app.xml ScriptUI is ready. Host logging disabled Debug tracing disabled Finished loading style definitions

    But debugging in Flash Builder with the debug Flash Player V10.1.53.64 produces no trace output in the file.

    Windows 7 x64

    Firefox 3.6.8

    David Salahi

    DavidSalahi
    DavidSalahi
    Known Participant
    August 5, 2010

    Have been researching this some more. Also, don't get any logging of trace statements from Flash Pro CS5. Furthermore, no logging of trace statements in Flashbug (for Firebug) nor in De MonsterDebugger although the MonsterDebugger does connect to the running SWF. No logging from the ActiveX version of the debug player in IE either.

    David Salahi

    T
    tcorbet
    Known Participant
    July 27, 2010

    I don't have the answer, but I think that there is now someone besides the AIR Runtime that is leaving the file locked.  I think if you try to clear the Trace file out of Firebug you have a pretty good chance of getting a #3013 error.  In my test environment, I can clear that by re-starting Firefox -- annoying, but at least it lets me get back to testing.

    R
    rootsounds-ihYz70Author
    Participating Frequently
    July 28, 2010

    There is no lock reported on the Trace log file.

    A
    Adobe Employee
    Alex J Harui
    Adobe Employee
    July 28, 2010

    Does the Flash Builder console work?

    J
    jdeeman
    Participant
    June 29, 2010

    I also have the same issue, so i can confirm its not an isolated problem.

    The only difference is that i'm running Windows 7.

    Any ideas on this would be much appreciated.

    A
    amshagar
    Participant
    July 27, 2010

    Same problem, my flashlog.txt is never fill... I don't understand why...

    With flashplayer 10.0.x : it's OK.

    R
    rootsounds-ihYz70Author
    Participating Frequently
    June 28, 2010

    Still stumped on this. I'm configured correctly (as far as I can tell). A known issue is that you can't debug while an AIR app is running because it holds a lock on the log file for some reason. This doesn't apply to my situation though.

    Works perfectly fine whenever I revert back to 10.0.x. I would like to actually be able to debug in the current build. That and benefit from the latest round of security fixes.

    P
    pauland
    Participating Frequently
    June 24, 2010

    I'm running that same version of the player and FlashBug/Firebug are working fine.

    R
    rootsounds-ihYz70Author
    Participating Frequently
    June 24, 2010

    I expect this was a sweeping 10.1 fail, the dev community would have been screaming bloody murder from the first pre-releases.

    As far as I can tell, the only change is the updated debug player. I did just update to XP SP3, but the former player works fine under it. I've run through the KB instructions to enable logging, but was already good to go. Maybe there's something minor that I'm missing or something that 10.0 tolerated that 10.1 is not so kind with.

    For the sake of completeness, here's my mm.cfg contents:

    ErrorReportingEnable=0 # Enables the logging of error messages.  0/1
    TraceOutputFileEnable=1 # Enables trace logging. 0/1
    MaxWarnings=100 # Sets the number of warnings to log before stopping.

    #flashlog - undocumented
    TraceOutputBuffered=0 # Traces will be buffered and write to disk multiple lines in one access
    AS3Verbose=0 # Traces detailed information about SWF ByteCode structure and Runtime parsing of the bytecode
    AS3Trace=0 # Trace every single call to any function that is being called in the SWF at runtime
    AS3StaticProfile=0 # Enables Just in Time Compiler (NanoJIT) logs.
    AS3DynamicProfile=0 # Shows dynamic information about the opcodes being called and gives statistic for each. The statistics include count, cycles, %count, %times and CPI

    #policyfiles
    PolicyFileLog=0 # Enables policy file logging
    PolicyFileLogAppend=0 # Optional; do not clear log at startup

    A
    Adobe Employee
    Alex J Harui
    Adobe Employee
    June 24, 2010

    Are you sure you installed a debugger version of 10.1?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices