Posted by
Blair McGlashan on
May 18, 2004; 9:52pm
URL: https://forum.world.st/Crash-and-burn-object-table-limits-tp3370595p3370607.html
"Dmitry Zamotkin" <
[hidden email]> wrote in message
news:c8c8g7$pnn$
[hidden email]...
> Hello Blair,
>
> > > I've used same technique to increase OT size for a long time, and
never
> > got
> > > same exception. I revealed only error message like "
> > > Unable to reserve memory for 33554432 objects. Please reduce maximum
OT
> > and
> > > restart." Unfortunately, this exception raises during saving of image
> and
> > I
> > > found no way to get rid of it except OT size reducing.
> >
> > You're running out of virtual memory address space. What is the size of
> your
> > paging file?
>
> My paging file size is 192 Mb.
>
That seems very small. Although in theory just reserving the memory for an
"object table" that can hold 33554432 objects (4x the default maximum size)
will not require an additional 384Mb of storage (which it would do if
committed, the object headers begin 12 bytes each), it does appear to be a
limitation in practice. Or perhaps you have really allocated a very large
number of objects and you are simply running out of virtual memory - when
the VM saves an image it requires double the space the OT normally occupies,
so although you might be able to load the image you will run out of memory
when trying to save it. Increasing your page file size will probably solve
the problem. Certainly on a 512Mb laptop with a 1024Mb paging file I can
find no problems with a maximum number of objects of 33554432.
BTW: You can use Chris Uppal's excellent Space Breakdown tool to get an
reasonably accurate approximation of the memory usage of the objects in your
image.
Regards
Blair