From: Aron Bartle (abartle++at++de-solutions.com)
Date: 05/31/2000 12:08:15
Performer People,
I've noticed that without sufficient performer memory, pfdLoadFile
prints an error message and aborts.
Wouldn't it be nicer if it were to return 0 or throw an exception? As it
is currently implemented, I can't gracefully recover from failing to
load a .pfb file.
____
Another approach would be to delete stuff and keep a sufficient amount
of performer memory free for loading files. Has anyone used arena info
'amallinfo' and understood how it works?
In my testing, the app died during pfdLoadFile with the message:
PF Fatal/Resource: pfMemory::new() Unable to allocate 59336 bytes from
arena 0x40c0000.
At that time, there was plenty of space in "ordinary" blocks in the
arena (7860912), but very little space in "small" blocks (16464). Does
usmalloc always require memory allocations under a certain size to come
from "small" blocks?
I was planning on writing an algorithm to swap nodes in/out of memory
based on when they need to be displayed. But without being able to catch
out-of-memory at pfdLoadFile, and without being able to predict when I'm
running out of performer arena space, it doesn't look so promising.
Thanks,
-Aron
-- Aron D. Bartle, Software Architect abartle++at++vrco.com 757.858.2800
This archive was generated by hypermail 2b29 : Thu Jun 01 2000 - 12:01:42 PDT