Posted by Chris Uppal-3 on May 17, 2004; 10:52am
URL: https://forum.world.st/Crash-and-burn-object-table-limits-tp3370595.html

Hi,

This one's probably for Blair.

First, and just FYI, I have now for the first time exceeded the default limits
of the OT in "normal" activity.  I.e. not benchmarking or purposely exploring
the system limits.

At least I assume that's why Dolphin just crashed with a dump (I can send it to
you if you want), as I was creating several million objects at the time.

Secondly, and more disturbingly, I followed the instructions on the Wiki for
increasing the OT size but it didn't work.  Before doing so I used a related
expression to print out the value of the SDWord at the relevant location (0x20)
and it seemed OK, 0x800000 (or however many zeros).  Then saved the image, then
reran the expression (being careful to ensure that the #position: was executed
again!), and then exited without saving.  I assume that's how to get the image
patched without overwriting the OT-size datum.

But the saved image won't re-load.   In fact Dolphin crashes trying to open it
:-(

According to VS the Dolphin application fails with
    Unhandled exception at 0x77c3dfa3 (msvcrt.dll) in Dolphin.exe:
    OxC00000005: Access violation writing location 0x10040000.

I'll keep that image for a few days in case you want to take a look at it.

I didn't loose any data, but obviously I'm not going to try increasing the OT
size again until this is working...

    -- chris