JPEXS Free Flash Decompiler Issue Tracker

If you are looking for the decompiler itself, visit

: The issue tracker is now writable again and logged users can download files too. But note that our support is very LIMITED.

List of issuesList of issues

#991 Serious Bug in Decompiler!
Author: user 1nd1g0
Date created:
Type: bug
Visibility: Everybody
Assigned to:
Labels: AS3Decompilation
State: closed Help

> What steps will reproduce the problem? Left-click on 'scripts' folder in Leftmost pane, then Right-click. Select 'Export selection' Save the scripts to wherever you desire. OK, fine But if you select a particular script in the Leftmost pane, and export it by itself, then the result may be different from the one in the Compilation. The individually exported script will be identical to the one visually presented in the Centre pane, but the one in the Compilation may be different. For example see the files uploaded. > What is the expected output? What do you see instead? I expect both the individually saved action script to be identical to the one in the Compilation produced by exporting the 'scripts' folder > What version of the product are you using? Is it "nightly build"? Which operating system do you have? v 6.0.1 major release Win 8.1 64 bit > Please provide any additional information below. If the problem is related to a SWF file, attach it here, otherwise we can't help you.
Download! (1,139 KiB)
This problem should be fixed in the latest nightly build.
State: new→upgraded
This is an ongoing problem. Exporting the scripts folder is very often subject to decompilation errors, which do not exist when the action scripts are exported individually. Bug needs to be addressed again!
Yes, I also noticed the exceptions. But the original problem is solved, right? So now there are no decomilation differences, max exception. I think this is a problem with parallel export. Did you try it with non-parallel mode?
Do you mean that I should untick the box in Settings > Parallel Speedup? (See attached 'PARALLEL EXPORT.PNG'
The problem should be fixed in the latest nightly.
I close this issue due to inactivity. Please create new issue if problem persists.
State: upgraded→closed