You should not get a signal 11 - SIGSEGV regardless of memory usage.
OpenDX uses its own memory allocator and should report an error when it
fails. Odds are (IMHO) memory has been corrupted by an error elsewhere.
I'd try running your network with "Print" replacing the Image (with no
args, so it doesn't print much) an see if the problem occurs. If it runs
all the way through, then in the Commands pulldown of the Message window,
select Show Memory Use. That'll cause it to rip through its free list
and is a simple non-conclusive method of checking for memory corruptuon.
Greg
"Wyn Williams"
<[EMAIL PROTECTED]> To:
[email protected]
Sent by: cc:
[EMAIL PROTECTED] Subject: [opendx-users] image
module not releasing memory
son.ibm.com
02/27/2003 02:51 AM
Please respond to
opendx-users
I have a network that imports a sequence of datafiles (3d vetor
field) (many thanks to those told me how to do it!) and uses
autoglyph to produce arrows which are rendered by the image
module.
The network looks like:
sequencer
|
format
|
MyOwnImportModule
|
autoglyph
|
image
after reading in 200 or so data files, the network fails with 'Signal 11
caught'
I used the 'usage' module to examine the memroy use, and the
used memory grew only when the image module was attached.
Naturally I thought that I maybe had a memory leak in my import
module, but as soon as I remove the image module, the memroy
usage remains constant as the sequencer reads in the files.
Can any suggest what might be going wrong ?
I am using OpenDx V 4.2.0 on a SUN Blade 100.
Thanks
Wyn
