From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 16c5e8,2b96cf32e9159fc5 X-Google-Attributes: gid16c5e8,public X-Google-Thread: 103376,2b96cf32e9159fc5 X-Google-Attributes: gid103376,public X-Google-Thread: f97e2,2b96cf32e9159fc5 X-Google-Attributes: gidf97e2,public From: Mats.Weber@elca-matrix.ch (Mats Weber) Subject: Re: STORAGE Errors Date: 1996/08/23 Message-ID: #1/1 X-Deja-AN: 176120441 references: <321CE2D6.3C8D@genesis.ac3i.dseg.ti.com> organization: ELCA Matrix SA newsgroups: comp.lang.ada,sanet.unix.questions,comp.lang.motif Date: 1996-08-23T00:00:00+00:00 List-Id: >My problem is that after a while of processing lists and displays I tend >to get storage exceptions that usually freeze the process. I've checked >and all the linked lists are deallocated when they are not being used and >all motif windows are destroyed when they are unmapped. Does anyone have >any information on STORAGE Errors or any suggestions on this particular >problem. First check that your program is not constantly eating memory while it executes. If it does, it has a memory leak. Memory leaks are not necessarilly your fault: the X11 libs you're using might leak, or the compiler might fail to deallocate some temporary memory (I've seen this happen). Another cause for storage_error in some implementations is an access violation (access to a memory address that you are not allowed to read/write) or erroneous usage of the memory allocator, such as deallocating the same object more than once (the standard recommends Program_Error, but some implementations do raise Storage_Error). Good Luck --Mats