Configuration:
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?
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
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.
I am on Windows XP Service Pack 3
My flashlog.txt is located at
"c:\Documents and Settings\[user name]\Application Data\Macromedia\Flash Player\Logs\flashlog.txt"
Under 10.1.51.66 Debug player "flashlog.txt" is filled with warnings due to https://bugs.adobe.com/jira/browse/FP-4615
Warning: 'StageVideo' has no property 'prototype'
Warning: 'AsBroadcaster' has no property 'addListener'
Warning: 'AsBroadcaster' has no property 'removeListener'
Under 10.1.53.64 Debug Player those warnings are gone (hurray) and flashtlog.txt file is correctly recreated every time.
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.
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
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
Just Close PS, i wrote an semi indept blog post about this
http://ihaveinternet.com/2010/08/05/scriptuiflexserver-and-flashlog-tx t/
And the Bug
Additional info from someone on the player team:
I tried TraceLogging and it is working for me just fine on WinXP SP3 for
both IE an FF.
The user mentions that he upgraded to SP3...is it possible he needs to reset
his HOMEPATH environment variable?
%HOMEDRIVE% %HOMEPATH%
(type, e.g., echo %HOMEPATH% at a command prompt)
Regarding the Win 7 user, the path to the log file has changed since the OS
changed and I believe it is now located in the SysWow or SysWow32 or
something like that. Sorry don't have a Win 7 machine at this time to locate
exactly. Also on Win Vista the path is different from XP
Vista: C:\Users\username\AppData\Roaming\Macromedia\Flash Player\Logs
I wish this tip worked for me as well. I have nothing open on OS X except
my browser, or Flash Pro, and still no flashlog.txt. I've even deleted the
Flash Player folder from /Users/me/Library/Preferences/Macromedia/. After
restarting my browser, FP recreates all the folders, but never writes a log.
Can somebody verify this mm.cfg for me? I've tried these two version with
no luck
mm.cfg 1
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.
Flex harUI wrote:
Additional info from someone on the player team:
I tried TraceLogging and it is working for me just fine on WinXP SP3 for
both IE an FF.
The user mentions that he upgraded to SP3...is it possible he needs to reset
his HOMEPATH environment variable?
%HOMEDRIVE% %HOMEPATH%
(type, e.g., echo %HOMEPATH% at a command prompt)
Regarding the Win 7 user, the path to the log file has changed since the OS
changed and I believe it is now located in the SysWow or SysWow32 or
something like that. Sorry don't have a Win 7 machine at this time to locate
exactly. Also on Win Vista the path is different from XP
Vista: C:\Users\username\AppData\Roaming\Macromedia\Flash Player\Logs
My HOMEDRIVE and HOMEPATH variables have indeed been messed with (thank you IT!). I've tried changing them to "C:" and "\Documents and Settings\<user> respectively in the command line using set. The changes register there, but still no logging. Not sure if maybe IT's environment variable settings stick behind the scenes in a fun, unintuitive way. Their values of course get reinstated on login.
The LiveDocs report that for XP log files are placed in: C:\Documents and Settings\username
whereas 95/98/ME places them in: %HOMEDRIVE%\%HOMEPATH
This perhaps suggests that there could be some different logic going on in XP which obviously changed with 10.1.
Hey guys,
Logging is working on my OS X box again, but only in Firefox, not Chrome.
Unsure if all the recent updates fixed it, or if reading this is what
helped.
http://livedocs.adobe.com/flex/3/html/help.html?content=logging_04.htm l
Here's what I learned, but unsure if it helped.
- Flash player looks for mm.cfg in the user's home directory first (
/Users/yourusername/ ), and then /Library/Appliations Support/Macromedia/
I was previously messing with mm.cfg in
/Users/username/Library/Preferences/Macromedia
- The path to flashlog.txt is now HARD CODED, and not configurable. If you
are on OS X, you should find your flashlog.txt file
at /Users/username/Library/Preferences/Macromedia/Flash Player/logs.
So for any OS X-ers have this problem, here's my setup.
- /Users/ericfickes/mm.cfg
ErrorReportingEnable=1
TraceOutputFileEnable=1
- My log file appears at
/Users/ericfickes/Library/Preferences/Macromedia/Flash Player/Logs
Hope this helps.
Eric Fickes = Independent Internet Contractor
Flex harUI wrote:
Additional info from someone on the player team:
I tried TraceLogging and it is working for me just fine on WinXP SP3 for
both IE an FF.
The user mentions that he upgraded to SP3...is it possible he needs to reset
his HOMEPATH environment variable?
%HOMEDRIVE% %HOMEPATH%
(type, e.g., echo %HOMEPATH% at a command prompt)
Regarding the Win 7 user, the path to the log file has changed since the OS
changed and I believe it is now located in the SysWow or SysWow32 or
something like that. Sorry don't have a Win 7 machine at this time to locate
exactly. Also on Win Vista the path is different from XP
Vista: C:\Users\username\AppData\Roaming\Macromedia\Flash Player\Logs
Still no luck. Corporate policy dictates those environment variables.
However, note that the above contradicts the information documented here which says that the path is hard-coded:
http://help.adobe.com/en_US/flex/using/WSda78ed3a750d6b8f-4867184d1239 f9d0558-8000.html
In 10.0 it must have been hard-coded, but obviously something changed in 10.1 and this isn't documented.
After being unable to get logging working since upgrading to 10.1, I fired up Sysinternals File Monitor and noticed that Flash Player is now looking for the mm.cfg file at %HOMEDRIVE%%HOMEPATH%\mm.cfg (IT remapped) for Win XP instead of C:\Documents and Settings\username\mm.cfg as it did in 10.0 and as the docs say. The flashlog.txt still goes in C:\Documents and Settings\username\Application Data\Macromedia\Flash Player\Logs though.
Not sure if this is a bug or a "feature" but it's annoying regardless.
phil_thomas wrote:
After being unable to get logging working since upgrading to 10.1, I fired up Sysinternals File Monitor and noticed that Flash Player is now looking for the mm.cfg file at %HOMEDRIVE%%HOMEPATH%\mm.cfg (IT remapped) for Win XP instead of C:\Documents and Settings\username\mm.cfg as it did in 10.0 and as the docs say. The flashlog.txt still goes in C:\Documents and Settings\username\Application Data\Macromedia\Flash Player\Logs though.
Not sure if this is a bug or a "feature" but it's annoying regardless.
This appears to definitely be the case. I managed to get IT to change my HOMEDRIVE and HOMEPATH mappings and it did the trick to get logging to work with 10.1. Considering that it's not documented and not at all configurable, I would classify this as a bug. It makes the debug player pretty much useless, so it should probably be addressed.
Tore my head apart on this one.. tried several permutations and combinations.The homepath/homedrive solution worked.
With version flash plugin 10,1,53,64 installed i got the log file to show up - My %HOMEDRIVE% was H: and my HOMEPATH was / - so i put mm.cfg in H:/ (i.e H:/mm.cfg is the complete path to the file) with the two lines
ErrorReportingEnable = 1
TraceOutputFileEnable = 1
and ran a swf (that had trace stmts) in a browser (IE) - The log file flashlogs.txt was created @ C:\Users\fred\AppData\Roaming\Macromedia\Flash Player\Logs
North America
Europe, Middle East and Africa
Asia Pacific