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#464 Javaw and ffdec open and closes
Author: 
capasha
capashaDate created:
Type: bug
Visibility: Everybody
Assigned to:
Labels: Installation
State: closed 
> What steps will reproduce the problem?
Installing ffdec 1.8.0u1
> What is the expected output?
Not to repeating itself in the processlist and the loading mouse cursor
What do you see instead?
Javaw open and closes with ffdec in the processlist and the loading mouse cursor
> What version of the product are you using? On what operating system?
1.8.0u1 Windows 7 x64
> 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
This have to do with the "add swf to context menu".
I don't understand your problem, please could you explain it to me?
If I click on "add swf to context menu" ffdec will add a new process in the processlist.
Which will try to close the new instance of ffdec. But opens again and closing forever.
I have reinstalled my harddrive twice today, and got the same problem when I installed
ffdec 1.8.0u1. Because of the swf to context menu in the installation process.
Tried nightly build, Still the same issue.
Please try the latest nightly build. FFdec open and closes bug should be fixed, but maybe
adding to the context menu is not working on your computer for soem reason. Please attach
the log files from C:\Users\username\AppData\Roaming\JPEXS\FFDec folder.
State: new→upgraded
I don't get any logs.
And is it working?
I still get the same errors as before. Javaw and ffdec open and closes 24/7 after I click
on "swf to context menu".
Please try to find the log files in Users folder, because i can't help without them.
The logfiles contains nothing. So nothing to post.
Here is a gif that shows what happens when I click on "swf to context menu"
https://www.mediafire.com/?b270pc4sd37jpua
The error I get after the files crashing after a while.
"The filename or filenameextension is too long"
picture: http://i.imgur.com/xjOuBdK.png
In the screenshot (video) i can see that you are using the version 7e28c238e13c. It was
created on 31st of December. I'be fixed this issuse on 1st os january.
I wrote here after i uploaded the fixed build, so please try the latest build.
Now it works. But no logfiles nor does it add to the context menu.
Found logfiles now,
18:19:42.697 > SEVERE: null
com.jpexs.decompiler.flash.console.ContextMenuTools addToContextMenu
com.sun.jna.platform.win32.Win32Exception
at com.sun.jna.platform.win32.Advapi32Util.registryGetStringValue(Advapi32Util.java:157)
at
com.jpexs.decompiler.flash.console.ContextMenuTools.addToContextMenu(ContextMenuTools.java
:117)
at
com.jpexs.decompiler.flash.console.ContextMenuTools.addToContextMenu(ContextMenuTools.java
:78)
at
com.jpexs.decompiler.flash.console.CommandLineArgumentParser.parseArguments(CommandLineArg
umentParser.java:179)
at com.jpexs.decompiler.flash.gui.Main.main(Main.java:805)
Are you administrator on your machine? Did you see the UAC window when tried to add (or
remove) the context menu item? Did you allowed to elevate the permission?
Please try the latest nightly build.
Tried latest nightly build. Without success. And yes I allowed the UAC window.
And is there any error message? Please attach the log file always.
Logfile is just the date and things, no errors.
19:56:57.133 > Date: 2014-01-03
19:56:57.136 > JPEXS Free Flash Decompiler v.1.8.0u1 nightly build 31dc47f3727e
19:56:57.136 > Windows 7 6.1 x86
19:56:57.136 > 1.7.0_45 Oracle Corporation x86
No idea why it saying that my OS is x86 when it's x64.
Probably you have installed 32bit java.
Please check the taskmanager. java.exe process. Is there a "*32" text after the process
name?
But i dont have more idea how to fix it on your machine, so i'll leave this issue for
Jpexs:)
State: upgraded→returned
Does the problem still exist?
I am closing this. Try version 4.0.1. If the problem persists, create new issue.
State: returned→closed