#2745 "The decompiler ran out of memory" when clicking "Raw edit"

If you are looking for the decompiler itself, visit https://github.com/jindrapetrik/jpexs-decompiler

NEW 03/07/2026: You can now close your own issues and reopen them later if needed. You can also comment closed issues.

List of issues

Author:

kjarosh

Date created: 08/07/2026, 8:23:52 am

Type: question

Visibility: Everybody

Assigned to:

Labels: Fonts GUI

State: opened Help

> What steps will reproduce the problem? 1. Open the SWF file 2. Find the DefineFont3 tag 3. Right click -> Raw edit > What is the expected output? What do you see instead? I expect to be able to edit the tag. In reality, the application freezes, CPU usage spikes, and after some time the OOM error is shown as a popup. > What version of the product are you using? Is it "nightly build"? Which operating system do you have? 26.2.1 on Flatpak > Please provide any additional information below. If the problem is related to a SWF file, attach it here, otherwise we can't help you.

font_test.swf (69 KiB)

JPEXS

08/07/2026, 9:05:49 am

It seems functional for me on Windows. On Flatpak, you probably need to enable more memory. I think it could be done by modifying a file named ffdec.sh in the app directory. and setting the value of variable FFDEC_MEMORY=1024m to something higher. Try it.

State: new→opened
Type: bug→question

kjarosh

08/08/2026, 1:01:29 pm

Thanks for looking into that. > On Flatpak, you probably need to enable more memory. > I think it could be done by modifying a file named ffdec.sh in the app directory. This file is a part of the app and it's read-only, I cannot edit it. The general pattern for providing configurable values would be through a config file (under $XDG_CONFIG_HOME) which the app can load instead of modifying the executables themselves. I did the following though and it worked FFDEC_MEMORY=2048m flatpak run com.jpexs.decompiler.flash I also checked the non-flatpak app (from GH releases, the exact same version, with -Xmx1024m) and it worked as well. So it looks like there are possibly two issues: 1. it takes (relatively) a lot of resources to "raw edit" a tag of a simple SWF, and 2. the flatpak app for some reason requires more resources than a non-flatpak app (maybe worth not using Xmx at all? people have different hardware and Xmx should be set dynamically for a desktop app in general).