- Bearbeitet
macOS - Spine 3.6.53 unable to start
Everything was working fine before the update but now Spine is stuck on "Starting Spine 3.6.53" and I can only force quit. A logfile for Spine is not created - macOS 10.13.5
When I start the executable from Terminal:
Spine Launcher 3.7.17
Mac OS X x86_64 10.13.5
Java 1.7.0_51 Esoteric Software
64-bit Server VM
Up to date: Spine 3.6.53
Spine 3.6.53 Essential
Licensed to: xxx
Intel Inc.
Intel Iris Pro OpenGL Engine
2.1 INTEL-10.34.27
Started.
java -version
java version "10.0.1" 2018-04-17
Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
Are you running antivirus, Finder "enhancements", or other software that may interfere with Spine? For example, Default Folder X causes Spine to hang and Rescue Time needs to be closed when Spine is started.
Nate schriebAre you running antivirus, Finder "enhancements", or other software that may interfere with Spine? For example, Default Folder X causes Spine to hang and Rescue Time needs to be closed when Spine is started.
I don't use any Finder enhancements or antivirus on this machine. Also it was working fine before the update (no software changed)
java -jar launcher-full.jar
Exception in thread "main" java.lang.NoClassDefFoundError: sun/misc/SharedSecrets
at com.esotericsoftware.spine.editor.launcher.y.EJ(Unknown Source)
at com.esotericsoftware.spine.editor.launcher.Launcher.main(SourceFile:1936)
Caused by: java.lang.ClassNotFoundException: sun.misc.SharedSecrets
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
Ok so I tried this on 3 different machines. No issue on 10.12.6 Sierra. Two of the other machines with High Sierra had the exact same issue (spinning wheel on loading). I uninstalled the entire pkg just now and removed every trace from the system. After that I ran the install and I was able to start it up one time without any issue. After closing and restarting the same issue returned. The only thing I did notice was that I used an app called "Moom" on both. This is the cause of the crash on the new version.
OK, thanks. Sorry you are still having trouble!
Spine doesn't use your system Java (it bundles its own Java) and is unlikely to work by running it with any other Java.
The first thing I suggest is to try downloading and reinstalling Spine. The latest launcher version is 3.7.19 and I see your log says Spine Launcher 3.7.17.
Your terminal logs show Spine starts fine and thinks it is running. By the time it has shown Started. it has created its window and loaded everything. The next and last thing it does is load the previously loaded project. If you don't see a Spine window, that is really odd!
You can try running jstack on Spine: jstack PID > stack.txt where PID is Spine's Java process ID, then post or email the stack.txt file. This will help us see what Spine is executing at that moment in time. It may help to do it a few times so we have a few snapshots of what it was doing. jstack is part of the JDK.
There are a couple easier things to try though.
You can specify the Spine version to use by creating a file called log.txt here (showing all OS paths in case others come across this post):
Windows: `<user home folder>\Spine\log.txt`
Mac: `<user home folder>/Library/Application Support/Spine/log.txt`
Linux: `<user home folder>/.spine/log.txt`
In the file put the version of Spine you want to use, eg 3.6.52. If that works then we at least narrow it down to something in 3.6.53.
New you can try resetting your preferences, stored here:
Windows: `<user home folder>\Spine\`
Mac: `<user home folder>/Library/Application Support/Spine/`
Linux: `<user home folder>/.spine/`
You can back up those files before going further, though just deleting the whole folder is OK, you'll just lose some settings, hotkeys, etc. If it does turn out that resetting your preferences fixes it, sending us the bad preferences files would be helpful.
First you can try deleting recent.json and try to start Spine. This stores your recently loaded project files and other paths. If Spine is choking trying to load a project, this may help.
Next delete the views.json file and try to start Spine. This is unlikely to help, but this can tell us if the problem is with Spine loading the view layout.
Next delete the prefs.json file and try to start Spine. This stores the rest of your settings.
Hopefully something there shines some light on the problem, if not we'll go from there. Best of luck!
Oops, we posted at the same time. To be clear, if you are running an app called Moom then Spine shows the hang-like behavior you've described?
Nate schriebOops, we posted at the same time. To be clear, if you are running an app called Moom then Spine shows the hang-like behavior you've described?
Yeah I did notice later that Spine uses a bundled jre. Yes, Moom is a window management tool which also adds some functionality to the Close/Minimize/Maximize-buttons (which I suspect cause the crash). Weirdly enough it did not crash on earlier versions. I switched to an alternative called Magnet and everything is working as previously. Thanks!
OK, great! I wish we knew why some OS X apps which hook into other apps cause problems with Spine. :S
Nate schriebOK, great! I wish we knew why some OS X apps which hook into other apps cause problems with Spine. :S
Java has known issues with the accessibility api from macOS. You may want to look into the cocoa accessibility api and try to make an objc wrapper https://developers.google.com/j2objc/guides/writing-native-methods. Quite annoying that macOS and tiling wm's are always special snowflakes in that regard^^