[vtkusers] Issues with large polydata datasets & capturing vt kOutputWindow data

[Wesley Brooks]

I changed a line in the boot.ini file from:

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows XP
Professional" /fastdetect

to;

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows XP
Professional"  /PAE /3GB /SOS /fastdetect

...and I still get the same problem. The error messages are identical
on each crash starting with;

ERROR: In d:\enthon\src\vtk-5.0\common\vtkDataArrayTemplate.txx, line 255
vtkFloatArray (60E35DD0): Unable to allocate 25166821 elements of size 4 bytes.

...and ending with;

ERROR: In d:\enthon\src\vtk-5.0\common\vtkDataArrayTemplate.txx, line 255
vtkFloatArray (60E35DD0): Unable to allocate 25166838 elements of size 4 bytes.

...with the number of elements increasing by three from one error
report to the next.

This error has been reported from three windows machines so far, and
on the most recent failure the memory usage by python was only
222,200kb.

Any further help would be greatly appreciated. Short of a major
re-write of a section of a large section of code (which is already in
the works) I'm running out of ideas!

Thanks for the help so far,

Wes.

On 29/08/2007, Wesley Brooks <wesbrooks at gmail.com> wrote:
> Just answered my own question. The redirection of the error output to
> a file works fine.
>
> in the error message text there are loads of lines very similar to the
> following:
>
> ERROR: In d:\enthon\src\vtk-5.0\common\vtkDataArrayTemplate.txx, line 255
>
> vtkFloatArray (60E35DD0): Unable to allocate 25166838 elements of size 4 bytes.
>
> ...so I'm hoping the flag in the ini file will fix the problem until I
> can re-write the code to be a little more memory friendly.
>
> Thanks again,
>
> Wes.
>
> On 29/08/2007, Wesley Brooks <wesbrooks at gmail.com> wrote:
> > Thanks for the help!
> >
> > I had a look for the vtkWin32ProcessOutputWindow but unfortunately
> > could not find it. It appears that it may not be wrapped for use with
> > python in the versions of vtk/python I have here. I had a further dig
> > around and found vtkFileOutputWindow which according to the included
> > documentation redirects the output to a file, from the error window.
> > One thing confuses me a little though, is this a global operation on
> > the imported vtk library? In other words do I need to tell the render
> > window directly what form of error output to use or just do somthing
> > similar to what follows at the beginning of my program (in python);
> >
> > errOut = vtk.vtkFileOutputWindow()
> > errOut.SetFileName('VTKERROR.txt')
> > vtkStdErrOut = vtk.vtkOutputWindow()
> > vtkStdErrOut.SetInstance(errOut)
> >
> > Thanks also for the tip about the flag in the boot.ini. I will try
> > this as soon as I have the above working but need to capture vtk error
> > messages better for error reports for the users to send to me.
> >
> > Cheers,
> >
> > Wes.
> >
> > On 28/08/2007, Nithiananthan, Sajendra
> > <Sajendra.Nithiananthan at rmp.uhn.on.ca> wrote:
> > >
> > > > -----Original Message-----
> > > >
> > > > Dear Users,
> > > >
> > > > My application using python/vtk/wxPython is crashing and I'd
> > > > appreciate any advice to help track and fix the error.
> > >
> > > > Also when the software crashes the vtkOutputWindow pops up as a
> > > > separate window flashes past a load of messages and then goes white.
> > > > Is there any way to capture the output to this window so I can review
> > > > it's contents to help with the bug tracking? I'm using the
> > > > wxVTKRenderWindow.
> > > >
> > > > Thanks for any help,
> > > >
> > >
> > > You can try using vtkWin32ProcessOutputWindow so that the popup is in a
> > > different window which won't die when your program crashes.  Sample C++
> > > code:
> > >
> > >         vtkWin32ProcessOutputWindow *outputwin =
> > > vtkWin32ProcessOutputWindow::New();
> > >         vtkOutputWindow::SetInstance(outputwin);
> > >         outputwin->Delete();
> > >
> > >
> > > -SN
> > >
> > > This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this e-mail may not be that of the organization.
> > >
> >
>