+ update 2020: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means we will NOT develop new features and/or fix most of bugs. We left the tracker running in case somebody from community would like to work on it. 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?
Open any flash file, go to text search and search something in AS.
> What is the expected output? What do you see instead?
Expected it to use multiple threads for decompilation. It only uses one core according to
task manager and decompilation is thus very slow (compared to 4 cores plus
> What version of the product are you using? Is it "nightly build"? Which operating system
do you have?
This seems to be happening on any version, even one that worked before. Though older
versions generally seem to be able to decompile faster.
Windows 10 Pro with latest updates installed.
> Please provide any additional information below. If the problem is related to a SWF
file, attach it here, otherwise we can't help you.
It actually seems like JPEXS uses the right amount of threads, but in reality only 1 core
is used. Could this have something to do with Windows?