My question was geared toward you in that I recall you had some similar hardware and recently started using the NT version...
I've not seen the red line you described. I have seen screen objects partially obscured by the background color in one frame and then be fully visible in the next. It could be a leak in the cache handling. It could accumulate in loop playback and cause memory to be used u. I also see it when doing a lot of interaction with different data and techniques, although not necessarily with long animation loop. Intermediate results fill up the cache and I run out of memory. It takes longer because I have done some optimization turning off things I really don't need to cache. Thanks. Chris Pelkie <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 07/12/2000 02:36:13 PM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: [email protected] cc: Subject: Re: [opendx-users] memory leak in 4.1.1/NT ? I haven't got the latest build, but do you observe the weird "red line" problem if you revisit a cached image that contained any full red colored objects? (horizontal red lines emanating from the right edge of red objects and projecting to the right edge of the image window). I suspect there's a problem in Image that got introduced between 3.1.4 and 4.x and was never found out until the OpenDX testing began, and that your bug and mine might be related through some internal mishandling of cache parameters. Wild guess on my part. Chris Pelkie Vice President/Scientific Visualization Producer Conceptual Reality Presentations, Inc. 30 West Meadow Drive Ithaca, NY 14850 [EMAIL PROTECTED]
