JPEXS Free Flash Decompiler Issue Tracker

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 issuesList of issues

#1844 JPEXS won't load sprites/images
Date created:
Type: bug
Visibility: Everybody
Assigned to:
State: new Help

> What steps will reproduce the problem? All system reqs are listed below. Steps required are to open up JPEXS with the attached scripts and just click on a non-script object. > What is the expected output? What do you see instead? Expected output would be sprites. Instead, whenever I click on anything sprite related, it freezes. When I run it w/ java from terminal, no debug statements. It looks like its running in an infinite loop. Works when viewing the p-code and actionscript, but not for anything else. > What version of the product are you using? Is it "nightly build"? Which operating system do you have? I installed ffdec_15.1.1.deb from https://github.com/jindrapetrik/jpexs-decompiler/releases. Not nightly. I'm running this on Ubuntu 20.04, AMD on x86_64 (though I don't think that should matter, as java is supposed to be portable). I'm using this version of java: ``` openjdk version "1.8.0_342" OpenJDK Runtime Environment (build 1.8.0_342-8u342-b07-0ubuntu1~20.04-b07) OpenJDK 64-Bit Server VM (build 25.342-b07, mixed mode) ``` I got my flash player from here: https://web.archive.org/web/20220325010638/https://www.adobe.com/support/flashplayer/debug_downloads.html > 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 the swf from here: https://uploads.ungrounded.net/534000/534198_penguins_attack_td_2.swf?1272212055. It's called penguins attack TD2.
user
The images started working for me for like 2 sessions, but now the window just isn't responding at all, regardless of whether I check an image or not. It just infinite loops on startup. I've checked if this is a ram issue, but I have like 3gb of ram free in /procinfo every time, so I don't think this is something werid to do with that. Can't think of any other possible sources for this issue for now. It's weird