[vtk-developers] Re: [vtkusers] vtk 4.4.2, python, vtkTkRenderWidget, crashes X11

[Burlen]

Prabhu, I have been able to reproduce the crash on a redhat 9 machine, running 
vtk4.2, so I am convinced it is NOT due to vtk 4.4!! The problem must be with 
in my code.

also I checked the vtk ccmake file,python binary and tk librarys with ldd, and 
all are matching OK.

I am guessing that the crashes have to do with creating and destroying 
vtkTkRenderWidgets, I notice this is a touchy opperation and in my first 
revision, I got a warning from vtk about destorying the window before the 
widget being "very bad", so I wrote code binding to the dialog box destory 
event so that I could call the vtkTkRenderWidget.destroy method before the 
window got destroyed....

I was browsing the mayavi sources, and notice a function to remove_actors, do 
you have to also remove actors from the render window before the destorying 
it???

what is the correct way to destroy a vtkTkrenderWidget aned its parent 
window???

my app, creates and destroys the vtkTkRenderWidget and its parent window many 
times in a session, so i have to get this right. I also have about 5-10 
actors in each scene, which get re-created for each render...

I really appreciate your advise.
Burlen






On Saturday 13 November 2004 01:58, Prabhu Ramachandran wrote:
> >>>>> "Burlen" == burlen  <burlen at apollo.sr.unh.edu> writes:
>
>     Burlen> Prabhu, thank you for the answer. This is a new machine,
>     Burlen> and I have just installed everything from scratch,
>     Burlen> including vtk, python and tcl/tk. my system doesn't have a
>     Burlen> _tkinter.so!! any where. on the other hand niether does my
>     Burlen> other system, which is not experiencing the crashes. both
>     Burlen> systems are nearly identical in terms of hardware and
>     Burlen> software, they have the same version of python, and tcl/tk
>     Burlen> as well. My new machine only has one version of tcl/tk,
>     Burlen> (so vtk and python aperently have been using the same
>     Burlen> library??)
>
> Could be a hardware problem?  CPU/GPU fan not running?
>
>     Burlen> I tried to track down the _tkinter python module
>
>     >>>> import imp imp.find_module("_tkinter")
>
>     Burlen> (None, '_tkinter', ('', '', 6))
>
>     Burlen> which means it is a C_BUILTIN, I think. So I don't know
>     Burlen> where this leaves me, do you have any other ideas?
>
> ldd on the Python binary (whereever that is) to see what libraries it
> links to.  In any case I'd advise that you rebuild Python, make these
> modules shared libraries, and try again.  I wonder why you need to
> build everything from source?  The standard RPM's/debs should work
> fine?
>
> cheers,
> prabhu