FS#37685 - [dart] Darteditor's jvm crashes with gtk internal callstack
Attached to Project:
Community Packages
Opened by drevilt (drevilt) - Thursday, 07 November 2013, 22:57 GMT
Last edited by Alexander F. Rødseth (xyproto) - Tuesday, 12 November 2013, 21:39 GMT
Opened by drevilt (drevilt) - Thursday, 07 November 2013, 22:57 GMT
Last edited by Alexander F. Rødseth (xyproto) - Tuesday, 12 November 2013, 21:39 GMT
|
Details
Description:
the Dart editor ( which is based on eclipse ) inside the newly included "dart" package in community crashes(segfaults) when you try to close a projects "pubspec.yaml" file with a gtk internal error. the logfile from the eclipse jvm is attached. This makes the darteditor hard to use as you cannot close some documents inside this modified eclipse because this crashes it. my guess is that, due to the dart package is not beeing built from source but just installing binaries, these binaries are built for ubuntu and not the latest upstream gtk as we use it. because of that there is an ABI mismatch between the darteditor binary and our current gtk version ( libgobject-2.0.so to be precise) . I think if the package would be built from source this problem would go away. I have tested this with oracle java and openjdk. Both fail, but i dont think this is a jvm dependent problem. Also the logfile show that i used version 0.8.10 of dart which is not yet in [community]. but the problem is the same with the current version in [community] 0.8.7. Additional info: * package version(s): * dart from [community] version 0.8.7.0 and ( selfbuilt ) 0.8.10.3 * config and/or log files etc. * log file from crashing eclipse is attached Steps to reproduce: - open darteditor - create a new project - open pubspec.yaml file from the new project - close the document - it should crash |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Tuesday, 12 November 2013, 21:39 GMT
Reason for closing: Upstream
Additional comments about closing: The dart package is now only the dart sdk.
Tuesday, 12 November 2013, 21:39 GMT
Reason for closing: Upstream
Additional comments about closing: The dart package is now only the dart sdk.
Your software contains an outdated version of swt, so it's a bug in your software.
What jre are you using?
1. File -> New Application (web application)
2. Open pubspec.yaml
3. Close pubspec.yaml (also tried changing something and saving)
I'm interested if anyone else can replicate this.
It's a known bug in SWT which has already been fixed upstream, but as long as software keeps shipping its internal outdated versions of swt this bug will still pop up now and then.
Closing this bug, since it does not appear to be a problem with dart.
Do you happen to know which package includes a library file that can work as a replacement for /opt/dart/libcairo-swt.so? I could not find any.
And were you thinking of this patch? http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=8a770faaa4942f4e1cde0428ab3348bcc4c88e3f
I don't see how it can be applied to the binary release of dart. One of the problems with dart is that the source is only provided as a whole bunch of source repositories, with the "gclient" tool from google for retrieving the right revisions of everything and making everything tick. It is a nightmare, and they currently do not have any source releases apart from this. A bug has been reported, requesting source releases per release version.
If the swt patch has to be applied to the dart sources for it to work as intended, it's an open question what to do next. Upstream should use the system wide library, if available, IMO.