: 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: new 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.
It would be nice if the applied deobfuscation could be rolled back, i.e. if the bytecode
could be reverted to its original state/contents before any deobfuscation. I know I can
reopen the file, but it can be very time-consuming if the file is 30+ MB or if I have
"Search All ActionScript" search results active.
Big file opening is much faster in the latest version then in version 1.x (when you
created this issue)
Search All Actionscript is still slow, but it is needed to decompile everything after
"deobfuscation rollback", so only the swf loading time matters.
So do you still need this functionality?