JPEXS Free Flash Decompiler Issue Tracker

If you are looking for the decompiler itself, visit

: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.

List of issuesList of issues

#1301 Cache files are still opened by java even after clear
Author: user zorzo
Date created:
Type: bug
Visibility: Everybody
Assigned to:
State: upgraded Help

> What steps will reproduce the problem? Open the attached file with "new SWF" in ffdec_lib. Call any clear cache methods or not, does not make a difference. I tried: SWF.clearAllStaticCache(); swf.clearAllCache(); swf.clearImageCache(); swf.clearModified(); swf.clearReadOnlyListCache(); swf.clearScriptCache(); swf.clearSoundCache(); swf.clearTagSwfs(); > What is the expected output? What do you see instead? Cache files should not be opened by the java process after. call "lsof -p ${pid}" and several "/tmp/ffdec_cache_..." files will be shown. > What version of the product are you using? Is it "nightly build"? Which operating system do you have? 9.0.0 on Ubuntu 16.04. > Please provide any additional information below. If the problem is related to a SWF file, attach it here, otherwise we can't help you. All cache files have 0 bytes, which I think is expected, the problem is the link that never closes. I use this on a java process that opens several SWF files and stays up indefinitely, after a few weeks I ran on opened files limit.
Downloadpage.swf (31 KiB)
Please try to disable the file caching: Cache.setStorageType(Cache.STORAGE_MEMORY) Since you are using the library, you not really need the file caching anyway. The big objects in the cache are the frames/shapes.
Worked flawlessly. Thanks
I think it is normal that the temp files exists until the swf object is alive (but only in cache mode STORAGE_FILES) even when the cache is cleared. May I close this issue?
State: new→upgraded
I still think there's something wrong, since my SWF objects are not alive when this happens. Anyway, It's not an issue for me anymore, since Cache.STORAGE_MEMORY is working just fine. If no one else is affected by this, you shouldn't waste time on this. So. Sure, close it. Thanks