AS3神秘宝藏 AVMINF: MTHD
最近装了flashdevelop 3.31版，每次debug编译会输出一大堆as3内部的处理情况，刚开始看着挺 好的，但是有时编译调试时都输出感觉有点麻烦，所以就上网找了下，下面是关闭的办法，
来源：
http://jpa lair.net/2010/02/10/mmcfg-treasure/
你可以编辑该文件，并使用以下开关。这些神秘开关可以帮助你调试 flash 程序。提供强大的的log功能。某些开关具有神奇的作用。
因为原文暂时无法访问，我就挑几个我感兴趣的注释一下。
如有谬误请指出
AllowUserLocalTrust
AS3AllocationTracking
AS3AutoStartSampling
AS3CSE
AS3DCE
AS3DynamicProfile
AS3MIR
AS3Sampling
AS3SSE
AS3StaticProfile
AS3Trace
AS3Turbo //加速
AS3Verbose //记得有用，忘记了怎么用
AssetCacheSize=X
AutoUpdateDisable
AutoUpdateInterval
AutoUpdateVersionUrl
AVHardwareDisable
CodeSignLogFile
CodeSignRootCert
Convert8kAnd16kA io
CrashLogEnable
DisableAVM1Loading
DisableDeviceFontEnumeration
DisableIncrementalGC
DisableMulticoreRenderer
DisableNetworkAndFilesystemInHostApp
DisableProd tDownload
Disable Sockets
DisplayGP lend //界面上小绿灯显示GPU加速是否在工作
EnableIncrementalValidation
EnableLeakFile
EnableSocketsTo
EnableSocketsTo
EnableSocketsTo
EnforceLocalSecurityInActiveXHostApp
ErrorReportingEnable
FileDownloadDisable
FileUploadDisable
ForceGP lend //强行启用GPU加速，即便你的显卡不再有效列表上
FrameProfilingEnable
FullScreenDisable
GCStats
GPULogOutputFileName
HeapProfilingAS3Enable
LegacyDomainMatching
LocalFileLegacyAction
LocalFileReadDisable
LocalStorageLimit
LogGPU
MaxWarnings
OverrideGPUValidation
OverrideUserInvokedActions
PolicyFileLog
PolicyFileLogAppend
PreloadSwf
PreloadSwf
Prod tDisabled
Prod tDownloadBaseUrl
ProfileFunctionEnable
ProfilingOutputDirectory
ProfilingOutputFileEnable
RendererProfilingEnable
RTMFPP2PDisable
RTMFPTURNProxy
ScriptSt kTimeout
SecurityDialogReportingEnable
SuppressDe buggerExceptionDialogs
ThirdPartyStorage
TraceOutputB?red //缓冲trace日志输出，分批次写入硬盘文件，能显著提高性能
TraceOutputFileEnable
TraceOutputFileName
UseBrokerProcess
WindowlessDisable
粘贴过来，不方便
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:
TraceOutputB?red = 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 tr, the traces will be b?red 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 str ture 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!
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:
TraceOutputB?red = 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 tr, the traces will be b?red 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 str ture 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!
粘贴过来，不方便
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:
TraceOutputB?red = 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 tr, the traces will be b?red 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 str ture 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!
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:
TraceOutputB?red = 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 tr, the traces will be b?red 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 str ture 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!
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!
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!
转载： http://bbs.9ria.com/thread-45161-1-1.html