It seems that examples/fwt/demo.fan on is broken on OS X. When run it crashes with the following output:
2009-04-04 14:02:41.343 java[41585:f603] An uncaught exception was raised
2009-04-04 14:02:41.345 java[41585:f603] objc_object* -[WebView
initWithFrame:frameName:groupName:](WebView*, objc_selector*, NSRect, NSString*,
NSString*) was called from a secondary thread
2009-04-04 14:02:41.346 java[41585:f603] *** Terminating app due to uncaught
exception 'WebKitThreadingException', reason: 'objc_object* -[WebView
initWithFrame:frameName:groupName:](WebView*, objc_selector*, NSRect, NSString*,
NSString*) was called from a secondary thread'
2009-04-04 14:02:41.347 java[41585:f603] Stack: (
2479997195,
2500730427,
2479996651,
2479996714,
2449942643,
2490071870,
106721554,
56121777,
56097407
)
/opt/fan/bin/fanlaunch: line 93: 41585 Trace/BPT trap $FAN_JAVA $osFlags $libPath
-cp "$FAN_CP" -Dfan.home="$FAN_HOME" $FAN_MAIN "$@"
I'm running OS X 10.5.6. The other FWT examples run fine.
I'm guessing it's a problem with the WebBrowser widget. Is this a bug in fan or SWT?
brianSat 4 Apr 2009
Is this off build 40 or the hg tip?
I just tried build 39 and 40 on my Macbook (10.5.2) and all seems to be working ok. Although I often get weird console spam with the WebKit plugin.
Although if it is crashing like that, it is most likely an SWT bug (or some way we are using SWT incorrectly).
kevykevSat 4 Apr 2009
It's off build 40, but I was getting the same error on build 38.
What version of SWT does fan use btw?
brianSat 4 Apr 2009
There is a version.txt in the swt jar you can check: version 3.448.
If you want to try a later version, just drop it into lib/java/ext/mac
kevykevSun 5 Apr 2009
Just to let you know, I tried running the examples with SWT 3.3 and got the same error. I also tried with SWT 3.5, but none of the examples would run with it (I reckon you need to recompile FWT to get it to work with 3.5).
I also confirmed that the SWT browser widget does work on my platform using Java, for SWT versions 3.3, 3.4 and 3.5-cocoa (tested using the SWT browser snippets). So I reckon the bug must be something to do with the way fan uses SWT.
kevykev Sat 4 Apr 2009
Hi,
It seems that
examples/fwt/demo.fanon is broken on OS X. When run it crashes with the following output:2009-04-04 14:02:41.343 java[41585:f603] An uncaught exception was raised 2009-04-04 14:02:41.345 java[41585:f603] objc_object* -[WebView initWithFrame:frameName:groupName:](WebView*, objc_selector*, NSRect, NSString*, NSString*) was called from a secondary thread 2009-04-04 14:02:41.346 java[41585:f603] *** Terminating app due to uncaught exception 'WebKitThreadingException', reason: 'objc_object* -[WebView initWithFrame:frameName:groupName:](WebView*, objc_selector*, NSRect, NSString*, NSString*) was called from a secondary thread' 2009-04-04 14:02:41.347 java[41585:f603] Stack: ( 2479997195, 2500730427, 2479996651, 2479996714, 2449942643, 2490071870, 106721554, 56121777, 56097407 ) /opt/fan/bin/fanlaunch: line 93: 41585 Trace/BPT trap $FAN_JAVA $osFlags $libPath -cp "$FAN_CP" -Dfan.home="$FAN_HOME" $FAN_MAIN "$@"I'm running OS X 10.5.6. The other FWT examples run fine.
I'm guessing it's a problem with the WebBrowser widget. Is this a bug in fan or SWT?
brian Sat 4 Apr 2009
Is this off build 40 or the hg tip?
I just tried build 39 and 40 on my Macbook (10.5.2) and all seems to be working ok. Although I often get weird console spam with the WebKit plugin.
Although if it is crashing like that, it is most likely an SWT bug (or some way we are using SWT incorrectly).
kevykev Sat 4 Apr 2009
It's off build 40, but I was getting the same error on build 38.
What version of SWT does fan use btw?
brian Sat 4 Apr 2009
There is a version.txt in the swt jar you can check: version 3.448.
If you want to try a later version, just drop it into lib/java/ext/mac
kevykev Sun 5 Apr 2009
Just to let you know, I tried running the examples with SWT 3.3 and got the same error. I also tried with SWT 3.5, but none of the examples would run with it (I reckon you need to recompile FWT to get it to work with 3.5).
I also confirmed that the SWT browser widget does work on my platform using Java, for SWT versions 3.3, 3.4 and 3.5-cocoa (tested using the SWT browser snippets). So I reckon the bug must be something to do with the way fan uses SWT.