Thread View: alt.windows98
4 messages
4 total messages
Started by Absys France
Thu, 25 Apr 2002 09:32
Problem of memory (win386.swf)
Author: Absys France
Date: Thu, 25 Apr 2002 09:32
Date: Thu, 25 Apr 2002 09:32
13 lines
1966 bytes
1966 bytes
We developed an application with C++ Builder running with Windows 98. This application make some calculation and some display. But if we load some datas several times, our hard drive memory decrease (even if we have free RAM). The file win386.swf increased during this operations. The only way we found to recover this memory was to shut down the computer. After this, win386.swf recover is normal size. If we do not shut down the computer every 30minutes, the program stop and this kind of message is diplayed : - Access violation at adress 410046EO in module 'BORLNDMM.DLL' write of adress 3E96BE16. or - C++ exeption How can we recover this memory lost during operation? Is it normal that win386.swf increase in size?
Re: Problem of memory (win386.swf)
Author: S.P. Goodman
Date: Thu, 25 Apr 2002 11:34
Date: Thu, 25 Apr 2002 11:34
22 lines
2256 bytes
2256 bytes
Have you tried to disallocate the memory used by the data file? I think the calloc/malloc functions have something to do with this. "Absys France" <absys.france@wanadoo.fr> wrote in message news:aa8i9r$n6t$1@wanadoo.fr... > We developed an application with C++ Builder running with Windows 98. This > application make some calculation and some display. But if we load some > datas several times, our hard drive memory decrease (even if we have free > RAM). The file win386.swf increased during this operations. The only way we > found to recover this memory was to shut down the computer. After this, > win386.swf recover is normal size. If we do not shut down the computer every > 30minutes, the program stop and this kind of message is diplayed : > - Access violation at adress 410046EO in module 'BORLNDMM.DLL' write of > adress 3E96BE16. > or > - C++ exeption > How can we recover this memory lost during operation? > Is it normal that win386.swf increase in size? > >
Re: Problem of memory (win386.swf)
Author: john thrum
Date: Sat, 27 Apr 2002 15:03
Date: Sat, 27 Apr 2002 15:03
33 lines
2529 bytes
2529 bytes
calloc/malloc are C style allocation functions. He shouldn't be using them in C++, he should be using new and delete (or delete[] for arrays). It's obviously a memory leak caused by improper de-allocation of resources. "S.P. Goodman" <earthlight2k@hotmail.com> wrote in message news:aa8pka$okl$1@helle.btinternet.com... > Have you tried to disallocate the memory used by the data file? I think the > calloc/malloc functions have something to do with this. > > "Absys France" <absys.france@wanadoo.fr> wrote in message > news:aa8i9r$n6t$1@wanadoo.fr... > > We developed an application with C++ Builder running with Windows 98. This > > application make some calculation and some display. But if we load some > > datas several times, our hard drive memory decrease (even if we have free > > RAM). The file win386.swf increased during this operations. The only way > we > > found to recover this memory was to shut down the computer. After this, > > win386.swf recover is normal size. If we do not shut down the computer > every > > 30minutes, the program stop and this kind of message is diplayed : > > - Access violation at adress 410046EO in module 'BORLNDMM.DLL' write of > > adress 3E96BE16. > > or > > - C++ exeption > > How can we recover this memory lost during operation? > > Is it normal that win386.swf increase in size? > > > > > >
Re: Problem of memory (win386.swf)
Author: S.P. Goodman
Date: Sat, 27 Apr 2002 22:31
Date: Sat, 27 Apr 2002 22:31
52 lines
3440 bytes
3440 bytes
Alas, by the time C++ came along I only dealt with testing the various compilers/environments popping up to support it. My sole calloc/malloc experience went back to 1985-6, actually, old mouldering knowledge only useable for solving problems with programs under the DOS 3.x days... "P Referring to your 'die spambot die' line... I wonder if someone can figure out a fragment of text to insert into one's address to make spambots cough up chunks. There ARE a lot of smart cookies out there who AREN'T helping spam companies after all, eh? "john thrum" <jomorisin@DIE_SPAMBOT_DIEAccess-4-Free.com> wrote in message news:aaeejo$s74$1@news.chatlink.com... > calloc/malloc are C style allocation functions. He shouldn't be using them > in C++, he should be using new and delete (or delete[] for arrays). It's > obviously a memory leak caused by improper de-allocation of resources. > > "S.P. Goodman" <earthlight2k@hotmail.com> wrote in message > news:aa8pka$okl$1@helle.btinternet.com... > > Have you tried to disallocate the memory used by the data file? I think > the > > calloc/malloc functions have something to do with this. > > > > "Absys France" <absys.france@wanadoo.fr> wrote in message > > news:aa8i9r$n6t$1@wanadoo.fr... > > > We developed an application with C++ Builder running with Windows 98. > This > > > application make some calculation and some display. But if we load some > > > datas several times, our hard drive memory decrease (even if we have > free > > > RAM). The file win386.swf increased during this operations. The only way > > we > > > found to recover this memory was to shut down the computer. After this, > > > win386.swf recover is normal size. If we do not shut down the computer > > every > > > 30minutes, the program stop and this kind of message is diplayed : > > > - Access violation at adress 410046EO in module 'BORLNDMM.DLL' write of > > > adress 3E96BE16. > > > or > > > - C++ exeption > > > How can we recover this memory lost during operation? > > > Is it normal that win386.swf increase in size? > > > > > > > > > > > >
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads