«
 
»

FlashLog.txt not being generated on OSX Leopard

I had this nasty problem on my leopard box. I installed flash tracer extension for firefox but nothing was displaied in…

Normally every traced line is written into flashlog.txt file…but actually no flashlog file was being generated! so problem wasn’t on that usefull extension but in flashplayer configuration.

So, here’s the solution i found out:
look for “mm.cfg” file into /Library/Application Support/Macromedia,
then open it with a text editor and write these two lines:

ErrorReportingEnable=1
TraceOutputFileEnable=1

Then save and restart flash player ( just restart your browser…).. Magically flashlog.txt is now being generated and flashtracer start working fine :D

NOTE: if you don’t find any mm.cfg file just create it with your text editor and put those 2 lines in it :)

Share and Enjoy:
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • LinkedIn
  • Live
  • Slashdot
  • StumbleUpon
  • Technorati
  • TwitThis

Related

Tags:

This entry was posted on Sunday, May 25th, 2008 at 7:42 pm and is filed under Flash Player. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

5 Responses to “FlashLog.txt not being generated on OSX Leopard”

  1. Manno Says:
    April 21st, 2009 at 4:59 am

    mm.cfg is generated automatically by some flash tracers, so you don’t need to worry about it. Check for example this tracer http://code.google.com/p/flash-tracer/
    This is really user friendly.

  2. Spencer Markowski Says:
    June 9th, 2009 at 2:53 pm

    Anyone having trouble on OS X with flash player 10.

    Look in ~/Library/Preferences/Macromedia/Flash\ Player/Logs/flashlog.txt

    Insanity!

  3. Erik P. Hansen Says:
    August 17th, 2009 at 11:47 pm

    Thanks for the post. It didn’t actually solve my problem, but it sort of did indirectly :) I just started compiling SWFs directly from TextMate and couldn’t figure out why the FlashLog.txt wasn’t getting updated. Turns out it was simply because I was compiling my SWF and not viewing it. Gotta actually OPEN the SWF to update the output file. Duh! Now to figure out if there’s a way to automatically open the SWF after fcsh compiles it… Hmm…

    Erik

  4. pigiuz Says:
    August 18th, 2009 at 12:38 am

    did you try maven with flexmojos plugin?
    maybe it’s a little cumbersome for a tiny production, but it solves many problems related to testing swfs, or better, the feature that could be useful to you is related to testing (maven is a really huge project with lots of features):
    actually it “forces” you to write test unit tests for your swfs which are executed once your code is compiled.
    everything is launched via command line, so it could be scareing if you’re not addicted to the terminal\propt, but once it is in your daily you’re done :)

  5. alooffool Says:
    March 16th, 2010 at 6:53 pm

    Here’s something else to check, if you can’t get your flashlog.txt to work. I created and saved my mm.cfg file in TextEdit, which by default saved it as RTF. Changing the mm.cfg file to ASCII text fixed the problem for me.

Leave a Reply