jpauclair

Because standing still is going backward…

AS3 hidden treasure in the mm.cfg file. Revealing and documenting many Flash secrets!

with 65 comments

When I found this, I just could not believed it.

In the past few weeks I did many articles greatly appreciated by the community: FlashPlayer Security, FlashPlayer Memory, AS3 Array under the hood, Optimized Base64 Encoding. But this one, I think, will rule them all!

I knew for a long time now that flash had undocumented features, little part of flash that could help speed up process (like the memory opcodes) or make interaction easy with right click and that kind of things. But I never thought that FlashPlayer would hide data that could help find bugs, or give better knowledge of how flash is interpreted.

As you may know, The mm.cfg files is located in:

  • Windows; C:\Documents and Settings\username\mm.cfg
  • OSX; /Library/Application Support/Macromedia/mm.cfg
  • Linux; home/username/mm.cfg
  • This file is interpreted when a Flash Player instance launches a SWF and gives indication of what should or shouldn’t be done.
    For example, most people use this file to set tracing parameters:
    ErrorReportingEnable=1
    TraceOutputFileEnable=1
    TraceOutputFileName=c:\logs\flashlogs.txt
    MaxWarnings=50

    Many other options are specified in the Adobe FlashPlayer Admin Guide… but most of is NOT DOCUMENTED!

    There is a LOT of thing to talk about and many cutting edge tools to improve your understanding of flash.

    So let’s get into it


    The Treasure

    The complete list of features of mm.cfg is at the end of the post, but first lets talk about what’s most interesting.
    I took my favorite 7 features and made detailed explanation with example for each one so here they are:


    TraceOutputBuffered = 1|0

    This feature is essential to the rest of all the cool features because they output A LOT of lines in the flashlog

    This is a very simple features but it change everything. Did you ever had problem tracing to many information and losing half of it in the flashlog?
    Well this is a known bug. If you make a loop of 1 000 000 and you trace the iterator, the flashlog will skip thousand of entries and will take 100% of your CPU while writing to disk.
    If you set this variable to true, the traces will be buffered and the write to disk will output multiple lines in one access.
    Performance? By default (without this feature), I’m able to trace 3600 line in 6 seconds and my CPU is at 100%.
    If I turn the features on, I can trace 1 000 000 lines in the same time! And my CPU is not even near 100%.



    AS3Verbose = 1|0

    This one is totally crazy.
    It traces detailed information about SWF ByteCode structure and Runtime parsing of the bytecode!
    You don’t need any software… no special framework to bind in your own SWF… just this one flag!

    verify Main/CallFoo()
        define incoming args
           @0  arg   0
           @1  arg   0
           @2  arg   0
           @3  arg   0
           @4  arg   0
           @5  arg   0
        alloc local traits
           @6  alloc 4
           @7  alloc 8
        alloc CallStackNode
           @8  alloc 48
        param 0
           @9  ldop  0(@5)
           @10               imm   4
        debug_enter
           @11               imm   0
           @12               imm   1
           @13               lea   0(@7)
           @14               lea   0(@8)
           @15               lea   0(@6)
        save state
           @16               def   @9
           @17               imm   165651400
           @18               st    0(@6) <- @17
           @19               usea  @16
           @20               st    0(@7) <- @19
           @21               def   @10
                    cse   @11
           @22               st    4(@7) <- @11
           @23               cm    MethodEnv::debugEnter (@3, @4, @5, @15, @12, @14, @13, @11)
           @26               ld    164427072(0)
                    cse   @11
           @27               ucmp  @26 @11
           @28               jne   @27 -> 0
           @29               alloc 0
                            stack:
                            scope: [global Object$ flash.events::EventDispatcher$ flash.display::DisplayObject$ flash.display::InteractiveObject$ flash.display::DisplayObjectContainer$ flash.display::Sprite$ Main$]
                             locals: Main@16
      0:debugfile "C:\Dev\src;;Main.as"
           @30               imm   164421632
           @31               ldop  44(@30)
           @32               imm   165988864
        save state
           @33               cm    Debugger::debugFile (@31, @32)
                            stack:
                            scope: [global Object$ flash.events::EventDispatcher$ flash.display::DisplayObject$ flash.display::InteractiveObject$ flash.display::DisplayObjectContainer$ flash.display::Sprite$ Main$]
                             locals: Main@16
      2:debugline 29
                    cse   @30
                    cse   @31
           @35               imm   29
        save state
           @36               cm    Debugger::debugLine (@31, @35)
                            stack:
                            scope: [global Object$ flash.events::EventDispatcher$ flash.display::DisplayObject$ flash.display::InteractiveObject$ flash.display::DisplayObjectContainer$ flash.display::Sprite$ Main$]
                             locals: Main@16
      4:getlocal0
           @38               use   @16 [0]
                            stack: Main@38
                            scope: [global Object$ flash.events::EventDispatcher$ flash.display::DisplayObject$ flash.display::InteractiveObject$ flash.display::DisplayObjectContainer$ flash.display::Sprite$ Main$]
                             locals: Main@38
      5:pushscope
                            stack:
                            scope: [global Object$ flash.events::EventDispatcher$ flash.display::DisplayObject$ flash.display::InteractiveObject$ flash.display::DisplayObjectContainer$ flash.display::Sprite$ Main$] Main@38
                             locals: Main@38
      6:debugline 31
                    cse   @30
                    cse   @31
           @39               imm   31
        save state
           @40               def   @38
           @41               use   @40 [0]
           @42               st    4(@7) <- @41
           @43               cm    Debugger::debugLine (@31, @39)
                            stack:
                            scope: [global Object$ flash.events::EventDispatcher$ flash.display::DisplayObject$ flash.display::InteractiveObject$ flash.display::DisplayObjectContainer$ flash.display::Sprite$ Main$] Main@40
                             locals: Main@16
      8:pushbyte 3
           @45               imm   3
                            stack: int@45
                            scope: [global Object$ flash.events::EventDispatcher$ flash.display::DisplayObject$ flash.display::InteractiveObject$ flash.display::DisplayObjectContainer$ flash.display::Sprite$ Main$] Main@40
                             locals: Main@16
      10:returnvalue
                    cse   @14
        save state
           @46               def   @45
           @47               cm    MethodEnv::debugExit (@3, @14)
           @49               use   @46 [2]
           @50               ret   @49
           @51               bb
    



    AS3Trace = 1|0

    This one is also very useful for debugging
    It trace every single call to any function that is being called in the SWF at runtime!
    It’s like expending the StackTrace to the full software run time.

    If you got a crash hard to find, you can turn this on and you will see ALL the last function executed that leaded to the crash.

    You can even see Timer Call and Events callbacks!

    1255552 AVMINF: MTHD ProfilerAgent/stopProfiling () @ 0x05DA35A0
    1255552 AVMINF: MTHD global/flash.sampler::stopSampling () @ 0x0A8C2B20
    1255553 AVMINF: MTHD flash.display::DisplayObject/get root () @ 0x0A8C06B0
    1255553 AVMINF: MTHD flash.events::EventDispatcher/removeEventListener () @ 0x0A8C2110
    1255553 AVMINF: MTHD flash.events::EventDispatcher/removeEventListener () @ 0x0A8C2110
    1255553 AVMINF: MTHD flash.events::EventDispatcher/removeEventListener () @ 0x0A8C2110
    1255553 AVMINF: MTHD flash.events::EventDispatcher/removeEventListener () @ 0x0A8C2110
    1255553 AVMINF: MTHD flash.events::EventDispatcher/removeEventListener () @ 0x0A8C2110
    1255553 AVMINF: MTHD flash.events::EventDispatcher/removeEventListener () @ 0x0A8C2110
    1255553 AVMINF: MTHD flash.net::Socket/flush () @ 0x0A8C2AD0
    1255553 AVMINF: MTHD flash.net::Socket/close () @ 0x0A8C2B70
    1255553 AVMINF: MTHD flash.net::Socket/_init () @ 0x0A8C0DF0
    1255553 AVMINF: MTHD flash.utils::Timer/stop () @ 0x0A8C2CB0
    1255554 AVMINF: MTHD flash.utils::Timer/reset () @ 0x0A8C1B20
    1255554 AVMINF: MTHD flash.utils::Timer/get running () @ 0x0A8C1C30
    1255554 AVMINF: MTHD flash.net::Socket/internalClose () @ 0x0A8C2D00
    1255554 AVMINF: MTHD flash.events::EventDispatcher/removeEventListener () @ 0x0A8C2110
    1255554 AVMINF: MTHD flash.utils::Timer/stop () @ 0x0A8C2CB0
    1255554 AVMINF: MTHD flash.system::System$/resume () @ 0x0A8C2D50
    1256675 AVMINF: MTHD flash.utils::Timer/tick () @ 0x0A8C2DA0
    1256675 AVMINF: MTHD flash.utils::Timer/_timerDispatch () @ 0x0A8C2FF0
    1256675 AVMINF: MTHD flash.events::TimerEvent () @ 0x0A8C3040
    1256675 AVMINF: MTHD flash.events::Event () @ 0x0A8C1AC0
    1256675 AVMINF: MTHD Main/OnTimer () @ 0x00B70910
    1256675 AVMINF: MTHD global/trace () @ 0x0A8C2170
    MyTimer
    1258705 AVMINF: MTHD flash.utils::Timer/tick () @ 0x0A8C2DA0
    1258705 AVMINF: MTHD flash.utils::Timer/_timerDispatch () @ 0x0A8C2FF0
    1258705 AVMINF: MTHD flash.events::TimerEvent () @ 0x0A8C3040
    1258705 AVMINF: MTHD flash.events::Event () @ 0x0A8C1AC0
    1258705 AVMINF: MTHD Main/OnTimer () @ 0x00B70910
    1258705 AVMINF: MTHD global/trace () @ 0x0A8C2170
    MyTimer
    



    AS3StaticProfile = 1|0

    This flag enable Just in Time Compiler (NanoJIT) logs.

    It gives detailed information on function conversion, bytecode conversion, MIR (machine-dependent intermediate representation) created, memory used and many others.
    At the end of execution, it also output a summary of all bytecode processed (For each opcode you have the number of occurrence, relatives importance, etc)

    size profile Main/CallFoo
      abc 12 mir 880 md 204
      1773K mir/s  74K md/s  96% in compile during 854 micros
      204 bytes from 55 MIR instructions 61 MD. max span 0 cse 7 dead 0
      76 bytes of stack with 5 spills 5 steals 5 remats using 0 times
    size profile Main/CallFooBar
      abc 23 mir 1088 md 262
      2386K mir/s  85K md/s  96% in compile during 921 micros
      262 bytes from 68 MIR instructions 76 MD. max span 0 cse 10 dead 0
      88 bytes of stack with 8 spills 7 steals 5 remats using 0 times
    
    verified instructions 3395
    verified code size 7441
    cpool size 0
    cpool int size 1
    cpool uint size 0
    cpool double size 0
    cpool string size 568
    cpool namespacesize 12
    cpool namespace set size 0
    cpool multiname size 75
    methods size 20100
    instances size 39
    classes size 2
    scripts size 8
    bodies size 82873
    
    18	0 %	36 B	0 %	 kill
    5	0 %	5 B	0 %	 label
    1	0 %	4 B	0 %	 ifngt
    10	0 %	40 B	0 %	 jump
    6	0 %	24 B	0 %	 iftrue
    22	0 %	88 B	1 %	 iffalse
    4	0 %	16 B	0 %	 ifeq
    4	0 %	16 B	0 %	 ifne
    2	0 %	8 B	0 %	 iflt
    2	0 %	2 B	0 %	 pushwith
    93	2 %	93 B	1 %	 popscope
    2	0 %	2 B	0 %	 nextname
    16	0 %	16 B	0 %	 pushnull
    2	0 %	2 B	0 %	 pushundefined
    79	2 %	158 B	2 %	 pushbyte
    6	0 %	19 B	0 %	 pushshort
    9	0 %	9 B	0 %	 pushtrue
    6	0 %	6 B	0 %	 pushfalse
    1	0 %	1 B	0 %	 pushnan
    50	1 %	50 B	0 %	 pop
    21	0 %	21 B	0 %	 dup
    2	0 %	2 B	0 %	 swap
    113	3 %	331 B	4 %	 pushstring
    43	1 %	86 B	1 %	 pushint
    11	0 %	22 B	0 %	 pushdouble
    202	5 %	202 B	2 %	 pushscope
    1	0 %	2 B	0 %	 pushnamespace
    2	0 %	6 B	0 %	 hasnext2
    143	4 %	382 B	5 %	 newfunction
    60	1 %	216 B	2 %	 callproperty
    102	3 %	102 B	1 %	 returnvoid
    9	0 %	9 B	0 %	 returnvalue
    13	0 %	26 B	0 %	 constructsuper
    9	0 %	30 B	0 %	 constructprop
    49	1 %	173 B	2 %	 callpropvoid
    4	0 %	8 B	0 %	 newobject
    5	0 %	10 B	0 %	 newarray
    2	0 %	2 B	0 %	 newactivation
    45	1 %	114 B	1 %	 newclass
    391	11 %	1011 B	13 %	 findpropstrict
    119	3 %	290 B	3 %	 findproperty
    96	2 %	197 B	2 %	 getlex
    158	4 %	432 B	5 %	 setproperty
    18	0 %	36 B	0 %	 getlocal
    18	0 %	36 B	0 %	 setlocal
    2	0 %	2 B	0 %	 getglobalscope
    9	0 %	18 B	0 %	 getscopeobject
    365	10 %	938 B	12 %	 getproperty
    174	5 %	443 B	5 %	 initproperty
    2	0 %	4 B	0 %	 getslot
    102	3 %	204 B	2 %	 setslot
    6	0 %	6 B	0 %	 convert_i
    11	0 %	11 B	0 %	 convert_u
    11	0 %	11 B	0 %	 convert_b
    6	0 %	14 B	0 %	 coerce
    3	0 %	3 B	0 %	 coerce_a
    7	0 %	7 B	0 %	 coerce_s
    1	0 %	1 B	0 %	 negate
    2	0 %	2 B	0 %	 increment
    6	0 %	6 B	0 %	 not
    6	0 %	6 B	0 %	 add
    4	0 %	4 B	0 %	 subtract
    1	0 %	1 B	0 %	 multiply
    5	0 %	5 B	0 %	 divide
    1	0 %	1 B	0 %	 lshift
    3	0 %	3 B	0 %	 rshift
    2	0 %	2 B	0 %	 bitand
    2	0 %	2 B	0 %	 bitor
    6	0 %	6 B	0 %	 equals
    2	0 %	2 B	0 %	 lessthan
    2	0 %	2 B	0 %	 greaterequals
    1	0 %	1 B	0 %	 increment_i
    275	8 %	275 B	3 %	 getlocal0
    49	1 %	49 B	0 %	 getlocal1
    36	1 %	36 B	0 %	 getlocal2
    17	0 %	17 B	0 %	 getlocal3
    13	0 %	13 B	0 %	 setlocal1
    14	0 %	14 B	0 %	 setlocal2
    11	0 %	11 B	0 %	 setlocal3
    23	0 %	144 B	1 %	 abs_jump
    54	1 %	330 B	4 %	 debug
    168	4 %	456 B	6 %	 debugline
    19	0 %	50 B	0 %	 debugfile
    



    AS3DynamicProfile = 1|0

    This one give dynamic information about the opcodes being called and gives statistic for each.
    The statistics include count, cycles, %count, %times and CPI

    My question is: Having access to the CPI (Cycle per instruction) will we be able to conclude all
    fights between what operation is faster that the others
    ? Cycle counts does not lies (on the same platform…)
    * Request for Jackson Dunstan: Wanna work on that? :) *
    But there is a problem with this one, it crash all the time.
    My guess is it can’t process “Flash Object” like Movieclip, Event, and all the other and only support operation valid in tamarin.

    total count=278 cycles=35508249 avg CPI=127727
    user      1.9%
    gc        0%
    decoder  97.7%
    verifier  1.6%
    codegen   0.2%
    count       cycles        %count    %time     CPI       opcode
    -----       --------      -------   -------   ---       ------
    2           34714742       0.7      97.7      17357371  decode
    211         602237        75.8       1.6      2854      verifyop
    6           89138          2.1       0.2      14856     codegenop
    3           78305          1.0       0.2      26101     newclass
    7           4813           2.5       0.0      687       findpropstrict
    6           3922           2.1       0.0      653       setslot
    4           3260           1.4       0.0      815       initproperty
    4           2724           1.4       0.0      681       getproperty
    9           1859           3.2       0.0      206       getlocal0
    4           1639           1.4       0.0      409       verifypass
    2           1190           0.7       0.0      595       returnvoid
    1           755            0.3       0.0      755       pushnamespace
    3           745            1.0       0.0      248       abs_jump
    2           550            0.7       0.0      275       findproperty
    5           527            1.7       0.0      105       pushscope
    1           403            0.3       0.0      403       pushnull
    2           382            0.7       0.0      191       pushbyte
    1           331            0.3       0.0      331       popscope
    1           331            0.3       0.0      331       pushundefined
    2           238            0.7       0.0      119       pushint
    2           158            0.7       0.0      79        pushdouble
    



    LogGPU = 1|0

    This enable logging GPU information about current SWF while it runs.
    Use GPULogOutputFileName = [path] to specify where to output that log.
    Use DisplayGPUBlend = 1 to display the little green square while GPU runs
    use ForceGPUBlend = 1 (At your own risk) to force GPU event if your videocard is not officially listed as valid for Flash GPU.

    [GPU-BLEND] SUCEEDED to create D3D device
    
    [GPU-BLEND]0x1161000 MONITOR/DEVICE SWITCH, old=0x0, new=0x18fd00
    
    [GPU-BLEND]0x1161000 Started (wMode=GPU) on device 10de 402 (6.14.11.9062) NVIDIA GeForce 8600 GT  mem:free=718, used=0
    
    [GPU-BLEND]Begin render aa=4.  Free TextureMem=712 Mb, Used = 5
    [GPU-BLEND]Using 0x13b7080 as RT vp= 0 0 800 600, aa = 4
    [GPU-BLEND]Clearing buffer 0x13b7080 { 0 0 800 600 } with color ffffffff
    [GPU-BLEND]Filling border & background on 0x13b7080 3 3 11 11 with bo:ffffffff, ba:ff00ff00
    [GPU-BLEND]Using 0x13b7080 as RT vp= 0 0 800 600, aa = 4
    [GPU-BLEND]End render
    
    [GPU-BLEND]0x1161000 Started (wMode=GPU) on device 10de 402 (6.14.11.9062) NVIDIA GeForce 8600 GT  mem:free=716, used=0
    
    [GPU-BLEND]Begin render aa=4.  Free TextureMem=712 Mb, Used = 5
    [GPU-BLEND]Using 0x11b7080 as RT vp= 0 0 800 600, aa = 4
    [GPU-BLEND]Clearing buffer 0x11b7080 { 0 0 800 600 } with color ffffffff
    [GPU-BLEND]Filling border & background on 0x11b7080 3 3 11 11 with bo:ffffffff, ba:ff00ff00
    [GPU-BLEND]Using 0x11b7080 as RT vp= 0 0 800 600, aa = 4
    [GPU-BLEND]End render
    




    PreloadSwf?flashvar1=value&…

    This is mainly used by the FlashBuilder Profiler. When you launch a SWF profiling, FlashBuilder add this line to mm.cfg to make it run another SWF before the one you profile.
    The default file is: C:/Documents and Settings/{USER}/My Documents/Flex Builder 3/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=9999
    The profiler agent is a SWF that use the as3 sampling classes to collect information and send them all over a socket connection to FlashBuilder.
    FlashBuilder is only interpreting that data received from the SWF
    By changing localhost by any other machine name you can connect to a remote FlashBuilder Profiler. On the Remote profiler you need to check the “wait for application” box and then start the local SWF on the other machine.

    This one is just crazy powerful: See: One SWF to rule them all! and New visual Profiler




    The Full List

      undocumented features will be written in bold


    AllowUserLocalTrust = 1|0

      Lets you prevent users from designating any files on local file systems as trusted.

    AS3AllocationTracking = 1|0

      Enable/Disable Profiling information (if turned off, we can’t profile Allocation in FlexBuilder anymore)

    AS3AutoStartSampling = 1|0

      Specify if we need a feedback before starting the profiler or we start right away.

    AS3CSE = 1|0

      CSE is an acronym for “Common Subexpression Elimination”. It seems plausible that these may be employed by the Flash virtual machine to optimize the byte-code before executing

    AS3DCE = 1|0

      DCE is an acronym for “Dead Code Elimination”. It seems plausible that these may be employed by the Flash virtual machine to optimize the byte-code before executing

    AS3DynamicProfile = 1|0

      When enabling this (you might crash half the time) the flash player is going to collect precious profiling information on opcodes used in the Swf (count/Time/%/Cycles)

    AS3MIR = 1|0

      Enable/Disable Profiling information (if turned off, FlashPlayer won’t keep information on Machine-dependant intermediate representation – NanoJIT)

    AS3Sampling = 1|0

      Enable/Disable Profiling information (if turned off, we can’t profile in FlexBuilder anymore)

    AS3SSE = 1|0

      *My guess is it turns on and off SSE optimization

    AS3StaticProfile = 1|0

      Information Generated by NanoJit (just in time compiler used in Tamarin), including a lot of statistic on code conversion, time to process and memory use

    AS3Trace = 1|0

      If turned on, ALL function called (at runtime) will be outputed in the flashlogs!
      You should always use in conjonction with TraceOutputBuffered=1

    AS3Turbo = 1|0

      ??

    AS3Verbose = 1|0

      Trace detailed information about SWF ByteCode structure and Runtime parsing of the bytecode!

    AssetCacheSize=X

      Lets you specify a hard limit, in MB, on the amount of local storage that Flash Player uses for the storage of common Flash components.

    AutoUpdateDisable = 1|0

      Lets you prevent Flash Player from automatically checking for and installing updated versions.

    AutoUpdateInterval = X

      Lets you specify how often to check for an updated version of Flash Player.

    AutoUpdateVersionUrl = [URL]

      Lets you specify a precise server to look up for new flash version

    AVHardwareDisable = 1|0

      Lets you prevent SWF files from accessing webcams or microphones.

    CodeSignLogFile

      ??

    CodeSignRootCert = 1|0

      ??

    Convert8kAnd16kAudio = 1|0

      ??

    CrashLogEnable = 1|0

      ??

    DisableAVM1Loading = 1|0

      If turned on, no SWF of version 8 and earlier can be loaded.

    DisableDeviceFontEnumeration = 1|0

      Lets you prevent information on installed fonts from being displayed.

    DisableIncrementalGC = 1|0

      Lets you enable/disable Garbage Collector Incremental policies (more info on the GC)

    DisableMulticoreRenderer = 1|0

      Lets you turn off multiple core rendering

    DisableNetworkAndFilesystemInHostApp = 1|0

      Lets you prevent networking or file system access of any kind.

    DisableProductDownload = 1|0

      Lets you prevent native code applications that are digitally signed and delivered by Adobe from being downloaded.

    DisableSockets = 1|0

      Lets you enable or disable the use of the Socket.connect() and XMLSocket.connect() methods.

    DisplayGPUBlend = 1|0

      If set to 1, it will prevent GPU use even if the SWF context is setted to use GPU and your card support it.

    EnableIncrementalValidation = 1|0

      ??

    EnableLeakFile = 1|0

      ??

    EnableSocketsTo = [address]

      Lets you create a whitelist of servers to which socket connections are allowed.
      EnableSocketsTo = localhost.localdomain
      EnableSocketsTo = 127.0.0.1

    EnforceLocalSecurityInActiveXHostApp = 1|0

      Lets you enforce local security rules for a specified application.

    ErrorReportingEnable = 1|0

      Set the ErrorReportingEnable property to 1 to enable the debugger version of Flash Player to write error messages to the log file.

    FileDownloadDisable = 1|0

      Lets you prevent the ActionScript FileReference API from performing file downloads.

    FileUploadDisable = 1|0

      Lets you prevent the ActionScript FileReference API from performing file uploads.

    ForceGPUBlend = 1|0

      Force GPU blending even if you video card is not officialy supported (At your own risk!)

    FrameProfilingEnable = 1|0

      Enable/Disable Profiling information (if turned off, we can’t profile Frames in FlexBuilder anymore)

    FullScreenDisable = 1|0

      Lets you disable SWF files playing via a browser plug-in from being displayed in full-screen mode.

    GCStats = 1|0

      Enable/Disable Profiling information (if turned off, we can’t profile GC in FlexBuilder anymore)

    GPULogOutputFileName

      Lets you specify the output file for the GPU informations

    HeapProfilingAS3Enable = 1|0

      Enable/Disable Profiling information (if turned off, we can’t profile Heap in FlexBuilder anymore)

    LegacyDomainMatching = 1|0

      Lets you specify whether SWF files produced for Flash Player 6 and earlier can execute an operation that has been restricted in a newer version of Flash Player.

    LocalFileLegacyAction = 1|0

      Lets you specify how Flash Player determines whether to execute certain local SWF files that were originally produced for Flash Player 7 and earlier.

    LocalFileReadDisable = 1|0

      Lets you prevent local SWF files from having read access to files on local hard drives.

    LocalStorageLimit = X

      Lets you specify a hard limit on the amount of local storage that Flash Player uses (per domain) for persistent shared objects.

    LogGPU = 1|0

      Lets you specify if you want to output debug GPU log

    MaxWarnings = X

      The default value of the MaxWarnings property is 100. After 100 messages, the debugger version of Flash Player writes a message to the file stating that further error messages will be suppressed.

    OverrideGPUValidation = 1|0

      Overrides validation of the requirements needed to implement GPU compositing.

    OverrideUserInvokedActions = 1|0

      ??

    PolicyFileLog = 1|0

      Enables the logging of policy file messages.

    PolicyFileLogAppend = 1|0

      Set the PolicyFileLogAppend property to 1 to save previous policy file log entries

    PreloadSwf?flashvar1=value&…

      Lets you specify a SWF to be loaded before the main swf.This is the profiler agent, a little flash app (ProfilerAgent.swf) that connect to the FlexBuilder Profiler via socket (localhost:9999).
      FlexBuilder is only interpreting that data.
      PreloadSwf=C:/Documents and Settings/{USER}/My Documents/Flex Builder 3/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=9999
      By changing localhost by any other machine name you can connect to a remote FlashBuilder Profiler. On the Remote profiler you need to check the “wait for application” box and then start the local SWF on the other machine.

    ProductDisabled = 1|0

      Creates a list of ProductManager applications that users are not permitted to install or launch.

    ProductDownloadBaseUrl

      ??

    ProfileFunctionEnable = 1|0

      Enable/Disable Profiling information (if turned off, we can’t profile function in FlexBuilder anymore)

    ProfilingOutputDirectory = [path]

      Specify where to save the ProfilerData file

    ProfilingOutputFileEnable = 1|0

      Specify if we want to create a file containing all the profiler data (flashprof_1265745253708.dat)

    RendererProfilingEnable = 1|0

      Enable/Disable Profiling information (if turned off, we can’t profile in FlexBuilder anymore)

    RTMFPP2PDisable = 1|0

      Specifies how the NetStream constructor connects to a server when a value is specified for peerID, the second parameter passed to the constructor.

    RTMFPTURNProxy = 1|0

      Lets Flash Player make RTMFP connections through the specified TURN server in addition to normal UDP sockets.

    ScriptStuckTimeout = X

      Lets you specify the time after what the timeout (too much time running a script) exception will popup

    SecurityDialogReportingEnable = 1|0

      Lets you specify whether the Security dialog should be visible or not.

    SuppressDebuggerExceptionDialogs = 1|0

      Lets you specify whether the Error dialog should be visible or not.

    ThirdPartyStorage

      Lets you specify whether third-party SWF files can read and write locally persistent shared objects.

    TraceOutputBuffered = 1|0

      Specify the flash player to use a buffer before writing to disk. If you had problem when tracing tousands of lines and line were skipped, this solve the thing. It’s also a lot faster (1000000 trace in 7 seconds instead of 3200 trace in 7 sec!)

    TraceOutputFileEnable = 1|0

      Set TraceOutputFileEnable to 1 to enable the debugger version of Flash Player to write trace messages to the log file.

    TraceOutputFileName= [path]

      (Before Flash 9) Sets the location of the log file. By default, the debugger version of Flash Player writes error messages to a file named flashlog.txt, located in the same directory in which the mm.cfg file is located.

    UseBrokerProcess = 1|0

      Lets you specify if you want to use elevated privileges or not (See the FlashPlayer update)

    WindowlessDisable = 1|0

      Lets you disable Floating Flash (ex: Ads)


    Conclusion

    This whole thing opens a new playground for hardcore programmer like me.
    A lot can be done with this new information:

  • Custom Profiling tool using AS3Verbose and AS3Trace modes
  • Custom Profiling tool using .dat generated by FlashProfiler
  • Automatic Code performance warning using NanoJIT structure analysis
  • Guide to performance using CPI (cycle per instruction)
  • Mapping of profiler using the PreloadSwf features (instead of localhost put any other host that have a valid profiler)
  • I didn’t have time to work extensively on each features and I may have interpreted incorrectly certain things.
    If it’s the case please tell me and I’ll modify this post. If you do test or benchmark using this post information please post them as comment here and I’ll add the benchmark later in the post.

    By the way, I am now on twitter: jpauclair

    add to del.icio.usAdd to Blinkslistadd to furlDigg itadd to ma.gnoliaStumble It!add to simpyseed the vineTailRankpost to facebook


    References

    Adobe MM.cfg documentation
    Adobe Flash Player Admin Guide (containing mm.cfg information)

    Written by jpauclair

    February 10, 2010 at 11:55 pm

    One blogger likes this post

    65 Responses

    Subscribe to comments with RSS.

    1. That’s awesome Jean, thanks for sharing!

      Here is some more official info on the PreloadSwf tag and custom profilers:
      http://livedocs.adobe.com/flex/3/langref/flash/sampler/package.html

      I’m guessing OverrideUserInvokedActions just bypasses the FP security model requirements for user-initiated events such as entering fullscreen mode.

      Congratulations on the blog and your excellent technical posts ;)

      Fernando França

      February 11, 2010 at 4:04 am

    2. Very useful, thanks for sharing

      Mario

      February 11, 2010 at 4:40 am

    3. This is amazing, thanks for sharing! I can definitely see custom profiling tools coming up (FDT, hint hint..)

      Antti Kupila

      February 11, 2010 at 5:35 am

    4. that’s a hell lot of hidden features :)

      thanks for all that!!

      zwetan

      February 11, 2010 at 5:46 am

    5. How weird ?

      I don’t have any mm.cfg file on my system –
      Is this really up-to-date with FP10 and CS4 ?

      As well It’s hard to believe to found this file on a “macromedia” folder.

      Any tips ?

      martial

      February 11, 2010 at 6:25 am

    6. Great post,

      Big thanks for all the infos provided.

      pleclech

      February 11, 2010 at 7:17 am

    7. Nice one!

      Thanks for this :)

      Andre

      February 11, 2010 at 7:35 am

    8. Unbelievable!

      Thanks!

      Alex

      February 11, 2010 at 7:56 am

    9. Wow, very nice finding. Beau boulot.

      ddrouin

      February 11, 2010 at 8:55 am

    10. [...] see AS3 hidden treasure in the mm.cfg file. Revealing and documenting many Flash secrets! by Jean-Philippe [...]

    11. Question about TraceOutputBuffered = 1|0

      It does not seem to work with plugins for FlashDev like FDtracer or FlashLog. I’m getting a Warning about the the file being used by another proccess…

      Any idea on how to turn on TraceOutputBuffered and still be able to access it at runtime from a log viewer?

      JPM

      February 11, 2010 at 12:37 pm

    12. Wow, a treasure trove indeed! How did you find all of these? As per your request regarding AS3DynamicProfile, I think I will take a look. I’ll certainly let you know what I find.

      Thanks for the documentation!

      Jackson Dunstan

      February 11, 2010 at 2:31 pm

    13. I think these might be wrong:

      AS3CSE = 1|0
      AS3DCE = 1|0
      Enable/Disable Profiling information (if turned off, we can’t profile in FlexBuilder anymore)

      CSE and DCE are acronyms for common compiler optimization techniques. It seems plausible that these may be employed by the Flash virtual machine to optimize the byte-code before executing. If this is the case, though, I can’t guess why this would affect your ability to profile. So I might be crazy.

      http://en.wikipedia.org/wiki/Common_subexpression_elimination
      http://en.wikipedia.org/wiki/Dead_code_elimination

      Joey Parrish

      February 11, 2010 at 4:51 pm

      • Thanks a lot, this make a lot of sense! I updated the post.
        I didn’t had that much time to try everything but still… thanks!

        jpauclair

        February 11, 2010 at 5:11 pm

    14. this is for very advanced users, but I guess some people will always dig for ‘undocumented stuff’ :)

      flash2nd

      February 11, 2010 at 7:30 pm

    15. [...] AS3 hidden treasure in the mm.cfg file. Revealing and documenting many Flash secrets! « jpauclair (tags: flash actionscript hack) [...]

    16. Absolutely incredible stuff!! How, may I ask, did you discover all of this awesomeness?

      Nate Chatellier

      February 12, 2010 at 12:22 am

    17. Excellent post.

      AS3Turbo :)

      simppa

      February 12, 2010 at 3:33 am

    18. ProductDownloadBaseUrl seems like nice target for malware authors

      makc

      February 12, 2010 at 4:58 am

    19. Thank you!

      ~o__O~

      So much properties!

      peko

      February 12, 2010 at 5:11 am

    20. TraceOutputBuffered is an interesting one; it would appear that it locks the flashlog so that only one instance of the player can write to it at a time; for me this meant if I had a browser open with a Flash App in one of the tabs, my standalone debug player would no longer output to the tracelog.

      Jonny Reeves

      February 12, 2010 at 5:43 am

    21. ProductDownloadBaseUrl:

      I’ll wager that this sets the base url for loading the air.swf when installing/updaing AIR apps from a Flash badge… among other things.

      mattjpoole

      February 12, 2010 at 5:43 am

    22. [...] AS3 hidden treasure in the mm.cfg [...]

    23. Awesome information, thanks for the explanation- especially the first two you introduced: TraceOutputBuffered & AS3Verbose
      Already helping me work better =)

      Evan Mullins

      February 12, 2010 at 11:52 am

    24. How did you find this stuff out? I ask because the list of mmcfg flags will probably change over time, and knowing your source would let me keep an eye on it when the player’s updated.

      Rezmason

      February 12, 2010 at 1:27 pm

    25. Wow, these are sweet. I wonder if some of these (particularly AS3StaticProfile) could be combined with a unit testing framework to get very some very detailed low level optimizations going where needed.

      Kevin Newman

      February 12, 2010 at 4:40 pm

    26. [...] it out over at http://jpauclair.net/2010/02/10/mmcfg-treasure/ Tagged as: Flash, mm.cfg, player Leave a comment Comments (0) Trackbacks (0) ( subscribe to [...]

    27. [...] can read all the features at: http://jpauclair.net/2010/02/10/mmcfg-treasure/ This entry was posted in General. Bookmark the permalink. Post a comment or leave a trackback: [...]

      mm.cfg file!

      February 12, 2010 at 5:29 pm

    28. Wow! very nice! A true wealth of information!
      Can a swf find out about the mm.cfg info somehow at run time?

      Tad

      February 13, 2010 at 1:49 am

    29. [...] #E3E9C0; display: none; } 6 Tweets Connect Pro Meeting Login 3 Tweets AS3 hidden treasure in the mm.cfg file. Revealing and documenting many Flash secrets! « jpauc… 3 Tweets Making It Look Great 7 – MoGraph Unleashed | Motionworks Cinema 4D [...]

    30. [...] Jean-Philippe Auclair пишет о недокументированных настройках, весьма занимательно. [...]

    31. Merci !!

      Fardeen

      February 15, 2010 at 11:13 am

    32. Thank you very much for this compilation. I found it very useful.

      However, for the longest time, I was stumped by the fact that the log file was not being created even though I had the proper settings in the mm.cfg.

      Then I came across a post (http://flashgamedevblog.blogspot.com/2007/06/debugging-flash-player-9-with-logfile.html) which said that Flash Player 9 ignored any customization of the log file location. Sure enough the file was there (Windows 7: %userprofile%\AppData\Roaming\Macromedia\Flash Player\Logs).

      Thanks again

      Sri Sankaran

      February 15, 2010 at 3:45 pm

    33. [...] AS3 hidden treasure in the mm.cfg file. Revealing and documenting many Flash secrets! [...]

    34. [...] AS3 hidden treasure in the mm.cfg file. Revealing and documenting many Flash secrets! « jpauclair [...]

    35. [...] a lot of options of the mysterious Flash Player (debug) configuration file have been revealed. Lots of interesting stuff, for the advanced, curious, and paranoid users too . May be we will see [...]

    36. [...] leave a comment » In my last article I introduced you to a bunch of features hidden in mm.cfg, [...]

    37. [...] hidden treasure in the mm.cfg file. Revealing and documenting many Flash secrets!http://jpauclair.net/2010/02/10/mmcfg-treasure/ 0 Comments No Comments so far Leave a comment RSS feed for comments on this post. TrackBack [...]

      AS3 Conversion

      February 18, 2010 at 7:41 am

    38. Are some of these features possible in AS2? i tried AS2Trace = 1 but it only logs my traces, i don’t see any list of functions

      Harry

      February 18, 2010 at 7:54 am

    39. Is this incorrect?

      DisplayGPUBlend = 1|0

      If set to 1, it will prevent GPU use even if the SWF context is setted to use GPU and your card support it.

      You’ve written above that it displays a green box when it’s being used… but below you write that it disables it. Are you sure it’s not supposed to be DisableGPUBlend along with DisplayGPUBlend?

      Nick

      February 18, 2010 at 1:16 pm

    40. Thanks for sharing some great info

      Ramon

      February 25, 2010 at 11:37 am

    41. Realy heavy! Maybe sometimes usefull!

      Ole

      March 11, 2010 at 11:45 am

    42. So was anything found about the crash that occurs when using AS3DynamicProfile ? I could _really_ use that function, but the debug player (started from FlashDevelop) crashes on startup when that flag is set.

      Swah

      March 12, 2010 at 4:29 pm

    43. [...] setting up the debug player for output on a different computer I found a posting by jpauclair. It talks about a ton of things that you can set in the mm.cfg file, not just the normal two that [...]

    44. [...] a comment » In the last posts, I talked about what you can get from mm.cfg setups but I didn’t give any GREAT example of [...]

    45. Wow, wow, wow, wow … This post rule !!!

      thienhaflash

      March 16, 2010 at 8:55 pm

    46. [...] drehen kann. Eine detaillierte Auskunft über nicht dokumentierte Einstellungen liefert der Artikel AS3 hidden treasure in the mm.cfg file von Jean-Philippe [...]

    47. Nice

      Danny

      April 27, 2010 at 6:20 am

    48. [...] output, which I could not explain. So I googled and there was only one – really great – pre CS5 blog, which shed light into this. So I searched for a mm.cfg file and found it where in the blog it was [...]

    49. Hi Sankaran,

      I looked inside my windows XP SP3 After installing Flash Professional CS5 and I did not file the mm.cfg
      I then did a windows search for *.cfg and no luck. Any ideas on how do I get Flash CS5 professional to generate this mm.cfg file automatically

      Flash

      May 11, 2010 at 9:19 pm

      • I think that it is not generated by default anymore. Still you can create it by hand in your DocumentsAndSettings/ProfileName/mm.cfg

        jpauclair

        May 11, 2010 at 9:33 pm

    50. [...] a). as3 hidden treasure in the mm.cfg fiel. Revealing and documenting many Flash secrets, – Windows, C:Documents and Settingsusernamemm.cfg b). Socket output server: [...]

    51. [...] AS3 hidden treasure in the mm.cfg file. Revealing and documenting many Flash secrets! [...]

    52. [...] could be useful for all swf with uncommented trace calls Read all the features here: http://jpauclair.net/2010/02/10/mmcfg-treasure/ By the way, this is the list of features he discovered (follow the link above for detailed [...]

    53. [...] I’ve found this page some time ago and I thought that this could prove useful someday, so I’ll just keep it here. mm.cfg is Flash Player configuration file that allows for some nice stuff – read more @ http://jpauclair.net/2010/02/10/mmcfg-treasure/ [...]

    54. thanks for the post man. I’ve updated my flash player 10 debugger today and it started crashing/ responding slowly. I’ve modified the mm.cfg file and it’s working properly now. but I’m a facing a problem now. I’m not able to see any server communication details(php echos) in the output console. Is there any setting for this? Any help would be much appreciated.
      cheers.

      ravi

      July 7, 2010 at 6:19 am

    55. Does anyone see anything in this list that will suppress warning messages, but not error messages? I’ve looked, but didn’t see anything, but my little brain doesn’t quite grasp everything in this list.

      I get the warning: “Warning” ‘flash has no property ‘prototype’ all the time – often multiple times per file – and it’s driving me crazy.

      Josh Knight

      July 23, 2010 at 2:05 pm

    56. [...] done through the profiler bundled in Flash Builder or through the Flash Player configuration file (mm.cfg). Those give you low level details about the VM but does not give you an overview of what is [...]

    57. i’m on mac osx snow leopard. Latest flash debug player installed and no mm.cfg file on /Library/Application Support/Macromedia !!! the file is not present on my hard drive. Does someone encountered the same problem ? Thanks.

      peace.lion

      August 31, 2010 at 1:20 pm

    58. Here’s some info on CrashLogEnable from Adobe:
      http://kb2.adobe.com/cps/839/cpsid_83973.html

      Samuel Crank

      September 3, 2010 at 2:06 pm


    Leave a Reply