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

#286 Saving file ended in 0 KB file
Author: user capasha
Date created:
Type: bug
Visibility: Everybody
Assigned to:
Labels: GUI
State: closed Help

> What steps will reproduce the problem? Trying to save an edited SWF-file. No errors or anything. > What is the expected output? Some errors and something so I know what's wrong. Not only a 0 KB file. What do you see instead? Saving the file ending in a file that is 0 KB. > What version of the product are you using? On what operating system? 1.6.7 on Windows 7 64bit > Please provide any additional information below. Attach the file you have problem with if neccessary. If you do not want to publish files YOU CAN CHANGE VISIBILITY TO PRIVATE
I can't fix anything without seeing the actual file and changes you made. Please attach it. (I can make issue private if you want)
took me around 3 hours and all i got was 0 KB. My friend get the same issue sometimes. All I did was added one new image with Sothink SWF Decompiler. Because the newest one gives too bright when I add an image. Then did I add these cases in Player I also added new values in items > ItemManager Attached the file.
Can I reproduce the bug somehow? I tried to replace an image with Sothink, then edit with FFDec the switch, but everythink looks fine to me.
Your error log is empty, isn't it? (c:\Users\<USER>\AppData\Roaming\JPEXS\FFDec\log.txt on windows)
Didn't know the logs was there. But I found the log for today,
I think the exception in the log is unrelated to 0kb file. In 1.7.0 I have changed it so SWF is written to temp file first and If it is not empty, then original file is overwritten. This should "fix" your problem.
State: new→upgraded
I am closing this, please create new issue when this happens again.
State: upgraded→closed