Re: [visad] Thread interrupt to prevent OutOfMemoryError

• To: Marius Schmidt <mariuss@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Subject: Re: [visad] Thread interrupt to prevent OutOfMemoryError
• From: Bruce Flynn <brucef@xxxxxxxxxxxxx>
• Date: Mon, 9 Aug 2010 11:55:06 -0500

Hi Marius,

DisplayImpl is an ActionImpl so I believe if you'd like to stop the display 
transformation you can make use of it's `stop` method.  But I suspect that 
you're running into issues reading the data in which case you'll have to stop 
whatever thread you're reading the netcdf file from.

--bruce


On Aug 8, 2010, at 12:41 PM, Marius Schmidt wrote:

> Hello again,
> 
> depending on the User interaction and current option settings, some longer 
> running method calls to the visad library (e.g. setReference for a 80MB 
> Netcdf Dataset that shall be mapped to RGBA and has be opened by Plain) 
> result in a Java OutOfMemoryError. I have a low memory notifier, that tells 
> me, if memory usage crosses a certain threshold, allowing me to react before 
> the error occurs. The opening and processing of the dataset happens in is own 
> thread. Unfortunately that thread does not react to interrupt request as soon 
> as processing has been started, so I have to kill it with the deprecated 
> Thread.stop method, if the OutOfMemoryError is near. Is there any possibility 
> to interrupt long running VisAD processing?
> 
> kind regards,
> Bergtroll
> 
> _______________________________________________
> visad mailing list
> visad@xxxxxxxxxxxxxxxx
> For list information, to unsubscribe, visit: 
> http://www.unidata.ucar.edu/mailing_lists/ 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

• References:
  • [visad] Thread interrupt to prevent OutOfMemoryError
    • From: Marius Schmidt