From: Andreas K. H. <and...@ph...> - 2010-03-15 09:56:31
|
This looks just like the problems I encountered on 0.18.3 on Gentoo. Sorry for not getting back to you so far. I did some quick tests with 0.18.5, saw problems and decided to investigate more before reporting. Then kept postponing this because of other stuff... More in the next days, Andreas > > - openvrml-player doesn't work at all. The best it manages is a single > > frame before crashing, and that only on extremely simple worlds. On at > > least a couple of occasions it chokes with signs of memory corruption: > > > > openvrml-player pngboxes.wrl > > ** (openvrml-xembed:26721): DEBUG: inserted reference to :1.197 > > get fences failed: -1 > > param: 6, val: 0 > > *** glibc detected *** /usr/local/libexec/openvrml-xembed: corrupted double-linked list: 0xb29b35e0 *** > > ======= Backtrace: ========= > > [snip] > > Ouch. > > The DEBUG message from openvrml-xembed is normal. Everything south of > that is not. > > I can reproduce this; I'll find out what's going on here. > > > and simultaneously this stuff showed up for any X event in the player window: > > > > ** (openvrml-player:26724): CRITICAL **: void<unnamed>::reset_fds(<unnamed>::CURLSource&): assertion `Invalid multi handle' failed > > [x many] > > That just means that openvrml-xembed has died unexpectedly and the > openvrml-player process doesn't know what to do. :-/ > > Are the other problem worlds publicly available? -- Dr. Andreas K. Huettel Institute for Experimental and Applied Physics University of Regensburg D-93040 Regensburg Germany tel. +49 151 241 67748 (mobile) e-mail ma...@ak... http://www.akhuettel.de/research/ |