- Editado
Bug - 2.1.02 Crashing when images altered outside Spine
Just got the latest Spine and I immediately noticed that if I change an image OUTSIDE of Spine which Spine is CURRENTLY using then it crashes. Didn't use to happen since I use that method all the time. As I side note - rolled my version back to 2.1.01 and all is well again.
Repro is:
- Open a Spine file
- Open Photoshop, edit and re-save an image currently used in Spine
- Try to go back to Spine (or just observe the crash)
- Happened every time I tried but I'll admit I didn't spend all night on a million repros
This is the log message it kicked out:
Spine Launcher 2.0.20-full
Windows 7 x86 6.1
Java 1.7.0-u6-unofficial Oracle Corporation
OpenJDK Server VM
Up to date: 2.1.02
[snipped personal info]
NVIDIA Corporation
GeForce GTX 660 Ti/PCIe/SSE2
4.4.0
Using customized hotkeys.
Started.
An unexpected error has occurred:
java.lang.NullPointerException
at oO.a(SourceFile:269)
at oQ.run(SourceFile:241)
at ad.e(SourceFile:247)
at ah.run(SourceFile:221)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:711)
at java.awt.EventQueue.access$000(EventQueue.java:104)
at java.awt.EventQueue$3.run(EventQueue.java:672)
at java.awt.EventQueue$3.run(EventQueue.java:670)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:681)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:244)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:147)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:139)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:97)
Thanks for listening,
-Tim
Thanks for the bug report!
I've notified Nate of this, if he can reproduce it, it will be fixed quickly.
Fixed in 2.1.03, thanks! Sorry for the trouble.
Looks like that did the trick!
Thanks Gents,
-Tim