: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.
State: upgraded new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
> What steps will reproduce the problem?
Try to decompile the attached SWF ("latest_upLynkOsmfPlugin.swf").
> What is the expected output?
At least for the decompilation to finish, even if the process throws an error.
Preferably to see the decompiled text - See attached TXT file from "showmycode.com"
> What do you see instead?
All CPU cores spike to 100% and the decompilation never completes.
> What version of the product are you using? On what operating system?
Using v2.1 - Also tried latest v5.3 - on Windows 7 and Windows Server 2008.
1) The SWF is obfuscated 2)Parts of the file were compiled using Flash C Compiler
We don't officially support these kind of files.
There are some deobfuscation technics in the decompiler which try to bypass some kinds of
obfuscation but it is not very effective. Maybe in the future we invent something
In current version (8.0) it should be better.
The FlashCC packages are slow to decompile. You can disable displaying of such packages in
Advanced Settings / Script / Ignore FlashCC-Alchemy or similar packages-