Welcome to NeoOffice developer notes and announcements
NeoOffice
Developer notes and announcements
 
 

This website is an archive and is no longer active
NeoOffice announcements have moved to the NeoOffice News website


Support
· Forums
· NeoOffice Support
· NeoWiki


Announcements
· Twitter @NeoOffice


Downloads
· Download NeoOffice


  
NeoOffice :: View topic - Odd console message, unexpected exit
Odd console message, unexpected exit
 
   NeoOffice Forum Index -> NeoOffice Testing
View previous topic :: View next topic  
Author Message
jimlaurent
Captain


Joined: Jun 23, 2003
Posts: 55

PostPosted: Mon Sep 20, 2004 8:16 am    Post subject: Odd console message, unexpected exit

While editing a presentation document mounted via SMB over a VPN, NeoJ 1.1 Alpha 1 patch 9 exited unexcpetedly. No crash log was generated.

This message was in the console window. Upon restarting Neo/J, no file recovery was performed. Mac OS 10.3.5



CGColorSpace.c:223: failed assertion `cs->shouldFree'

sh: line 1: crash_report: command not found

CGColorSpace.c:223: failed assertion `cs->shouldFree'





Fatal exception: Signal 6

Please turn on Enable Crash Reporting and

Automatic Display of Crashlogs in the Console application

CGColorSpace.c:223: failed assertion `cs->shouldFree'

sh: line 1: crash_report: command not found





Fatal exception: Signal 6

Please turn on Enable Crash Reporting and

Automatic Display of Crashlogs in the Console application
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Mon Sep 20, 2004 9:12 am    Post subject:

Jim,

I think we saw the same "CGColorSpace.c:223: failed assertion `cs->shouldFree'" message in Neo/J 0.8.x. IIRC, this error happens when the underlying OOo code disposes of images in a different order than they were created. I think JVM keeps track of these color space objects in a stack. I will have to think how I can implement delayed disposing of images that OOo disposed out of order.

As for Neo/J not saving a recoverable file, that seems very strange since the "crash reporting" text is generated by the underlying OOo code. So, clearly OOo's crash handler code is being run but the crash handler code is not saving a recoverable file. Have you seen this behavior in OOo X11?

Patrick
Back to top
jimlaurent
Captain


Joined: Jun 23, 2003
Posts: 55

PostPosted: Mon Sep 20, 2004 9:48 am    Post subject:

I really haven't used OO for X11 since Neo/J 0.8.4 became fast and usable.
Back to top
Display posts from previous:   
   NeoOffice Forum Index -> NeoOffice Testing All times are GMT - 7 Hours
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © Planamesa Inc.
NeoOffice is a registered trademark of Planamesa Inc. and may not be used without permission.
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.