OK, that's also possibly why I have been experiencing strange crashes
upon loading large images into a hidden stack, reading their image data,
importing RGB values into a table in sqlite database, deleting image and
closing. Then if I open another image within the same handler
application mysteriously crashes PC with 2 GBytes of RAM... Vote cast.
Viktoras
Ben Rubinstein wrote:
Notwithstanding that Derek's case seems actually have been different:
I certainly have run afoul of this problem, that there is no garbage
collection until a handler ends, in a similar situation: a script
where image objects were created and deleted, when given a large
enough job on a machine with small enough memory, caused the app to
crash.
http://quality.runrev.com/qacenter/show_bug.cgi?id=6791
There are certainly ways this behaviour could be improved, without
impairing performance.
Ben
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution