spectacular crash

From: Frank Andreas de Groot (nospam_at_abcdefgnospam.biz)
Date: 12/26/03 

Date: Fri, 26 Dec 2003 03:35:46 +0100

I just Ctrl-clicked on an array in debugging mode.
After waiting 2 minutes, Delphi crashed & aborted.

I suspect the reason is that the array had 32 million elements.

Relevant Pages

  • Re: About Thread Completion Notify.
    ... This is the reason that i must keep track of the threads and they have to ... i remove it from the array. ... > (which you probably don't since you are servicing requests in separate ... you shouldn't have a need for waiting on events. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: KeWaitForMultipleObjects
    ... > It's not obvious from the DDK docs. ... Actually I don't understand reason why ... > objects' array should be accessed while the thread is waiting. ...
    (microsoft.public.development.device.drivers)
  • Re: spectacular crash
    ... > I suspect the reason is that the array had 32 million elements. ... Did you report it in Quality Central? ...
    (borland.public.delphi.non-technical)
  • Re: spectacular crash
    ... > I just Ctrl-clicked on an array in debugging mode. ... > I suspect the reason is that the array had 32 million elements. ...
    (borland.public.delphi.non-technical)
  • Re: please confirm something (jdbc)
    ... of its internal buffer so that will double the amount of memory that you need. ... That's the reason I wrote my own dynamic byte array ... Given all the memory re-allocation that goes on inside the ByteArrayOutputStream anyway, I'm not sure that one more allocation is all that much extra overhead. ... If I have two ways of coding something, and I know that one will definitely use less memory (or be quicker for whatever reason) then I will choose the one "better" one. ...
    (comp.lang.java.programmer)