[XSTR-709] XStream 1.4.3 locks up on a Mac

Details

Type: Bug
Status: Closed
Priority: Critical
Resolution: Fixed
Affects Version/s: 1.4.3
Fix Version/s: 1.4.4
Component/s: Core
Labels:
None

JDK version and platform:
1..6.0_29 on a OSX 10.7

Description

When using xstream 1.4.3 on a Mac, it simply locks up a thread.
Note that this affects Macs ONLY. Code is fine on Windows and Linux.

Debugging shows that line 38 in class com.thoughtworks.xstream.core.JVM never exists from the 'loadClass("java.awt.Color")'

Attached is the stack trace.

Further investigation shows that this is a known problem on Macs and that loading class java.awt.Color has nasty side-effects which cause threads to lock up on some cases.

Proposed solution:
either load a different class, or find a different way to test whether AWT is present.

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

stack_trace.png

234 kB

18/Oct/12 11:11 AM

Issue Links

is related to

MWAR-295 weird icon on mac due awt toolkit setup

Activity

Hide

Permalink

Jörg Schaible added a comment - 18/Oct/12 5:42 PM - edited

This seems to be the same problem as reported in eclipse bug database: https://bugs.eclipse.org/bugs/show_bug.cgi?id=345652

Another thread: http://lists.apple.com/archives/java-dev/2008/May/msg00116.html suggest that some other awt classes do load fine, seems like java.awt.Color is a bad choice to just check if the AWT is present.

Hmm. No solution yet. When I try to load AWTError, it succeeds, but an installation without AWT support will fail later then. Same applies, when I try to load Color without initializing the class :-/

What happens when you call

Toolkit.getDefaultToolkit()

directly before you initialize XStream?

Show

Jörg Schaible added a comment - 18/Oct/12 5:42 PM - edited This seems to be the same problem as reported in eclipse bug database: https://bugs.eclipse.org/bugs/show_bug.cgi?id=345652 Another thread: http://lists.apple.com/archives/java-dev/2008/May/msg00116.html suggest that some other awt classes do load fine, seems like java.awt.Color is a bad choice to just check if the AWT is present. Hmm. No solution yet. When I try to load AWTError, it succeeds, but an installation without AWT support will fail later then. Same applies, when I try to load Color without initializing the class :-/ What happens when you call Toolkit.getDefaultToolkit() directly before you initialize XStream?

Hide

Permalink

Daniel Kulp added a comment - 27/Nov/12 11:20 AM

This change also has a side effect (even if you call Toolkit.getDefaultToolkit()) of having the "Java" icon bounce onto the Mac Dock even for applications that have no need or use for anything related to AWT.

Show

Daniel Kulp added a comment - 27/Nov/12 11:20 AM This change also has a side effect (even if you call Toolkit.getDefaultToolkit()) of having the "Java" icon bounce onto the Mac Dock even for applications that have no need or use for anything related to AWT.

Hide

Permalink

Jörg Schaible added a comment - 29/Nov/12 4:15 PM

I think I detected the change in 1.4.3 that caused the problem and found an alternative. Please test the new SNAPSHOT.

Show

Jörg Schaible added a comment - 29/Nov/12 4:15 PM I think I detected the change in 1.4.3 that caused the problem and found an alternative. Please test the new SNAPSHOT.

Hide

Permalink

Jörg Schaible added a comment - 15/Jan/13 6:08 PM

I've revisited the bug fix again and I think it was still not working. New SNAPSHOT deployed again. That one will be released, if I get no other feedback.

Show

Jörg Schaible added a comment - 15/Jan/13 6:08 PM I've revisited the bug fix again and I think it was still not working. New SNAPSHOT deployed again. That one will be released, if I get no other feedback.

People

Assignee:

Jörg Schaible

Reporter:

Timotej Ecimovic

Votes:

0 Vote for this issue

Watchers:

3 Start watching this issue

Dates

Created:

18/Oct/12 11:11 AM

Updated:

19/Jan/13 8:12 AM

Resolved:

29/Nov/12 4:15 PM