If you are looking for the decompiler itself, visit https://github.com/jindrapetrik/jpexs-decompiler
NEW : We have got a new blog where we post some interesting SWF internals info.
List of issues#2076 Rename identifiers broke after a certain version
Author: 
ODAKAB
ODAKABDate created:
Type: bug
Visibility: Everybody
Assigned to:
Labels: Rename identifiers
State: closed 
> What steps will reproduce the problem?
1. Install JPEXS 18.5.0
2. On top of default settings, enable automatic deobfuscation and simplify expressions
(not sure if these are related)
3. Enable auto rename identifiers (Enabling this will trigger the issue)
4. Attempt to load swf in question, watch how ram usage keeps ramping up forever (20GB and
keeps going) like it stuck in an infinite loop or recursion, renaming identifiers will
never succeed (or will it take 10x longer?)
> What is the expected output? What do you see instead?
While using JPEXS 18.3.5 ram usage stays below 5GB, scripts successfully load in around 1
minute.
> What version of the product are you using? Is it "nightly build"? Which operating system
do you have?
JPEXS 18.5.0 (broken)
JPEXS 18.3.5 (working)
Windows 10 22H2 (19045.3324)
Oracle JDK 17.0.4.1
> Please provide any additional information below. If the problem is related to a SWF
file, attach it here, otherwise we can't help you.
main.swf (13,013 KiB)Does v18.3.6 work? The changelogs appear to show a number of fixes to renaming invalid
identifiers there. It would be very handy to narrow down the issue to a specific version
so finding the culprit is easier, unless you have done that already.
PR178 - infinite recursion when getter/setter calls same property of superclass
The current nightly build also seems to fix something relating to infinite recursions so
you could give that a shot too to see if your issue is already fixed.
This is fixed in nightly 2575, please try it.
State: new→upgraded
Tested with 18.5.0 nightly 2584 and renaming identifiers work fine. However on extraction
i faced an Error popup while using same main.swf file and i never had any Error popup
while using JPEXS before. Is it more verbose now or another issue with newer versions?
Error occured: Cannot read field "abc" because "ci" is null (Picked ignore all after
retrying two times)
I couldn't notice anything odd or worse than before on exported scripts so far.
What do you mean by "extraction"?
Please tell me exact steps how to reproduce the problem on this swf file.
Then I can fix it. Thanks.
Sorry, I meant exporting scripts.
Settings: I have Automatic deobfuscation, Simplify expressions, Auto rename identifiers,
and everything except GraphViz configured on Paths.
When i export scripts i faced an Error popup: Cannot read field "abc" because "ci" is
null
Clicked ignore all, and didn't notice anything wrong with exported scripts compared to
18.3.5
So i don't have any complaints i just wonder if these popups are new and app is made more
verbose or there's a new problem
The problem with export should be fixed in nightly 2590, try it.
Tested with 18.5.0 nightly 2594, couldn't spot any issues.
Thank you and all the contributors working on project.
State: upgraded→closed