Commodity bug
4 messages in this thread
I killed myself trying to figure out a 264 byte memory leak in a commodity
program I wrote. I just couldn't understand it. On a wild thought, I tried
a couple of other commodities and, lo and behold, each and every commodity
(including ones from Commodore itself) lose 264 bytes each time the
commodity's window is called up with its hotkey. Hide it and recall it 10
times and you lose 10 x 264 bytes.
Is this a commonly known bug? Is this documented or fixed somewhere? This
hardly seems tolerable.
David Czaya …via AutoPilot
73445,407
264 bytes, once, doesn't sound like alot at first, but if you need a
non-stop system that could be serious trouble!
Sounds like somebody ought to log on to BIX and ask the C= folks. I'm not
gonna do it! I'm still paying for the access to it, but I can't stand
using it!
Of course there are several registered developers out here who might pose
the question…
Robb
I'm only getting a temporary 264 byte loss here, but I'm running a Beta WB
and I only have the C= blanker running.
I lose 264 bytes the first time I bring up the blanker's window, then
memory usage stays constant untill I do an "avail flush" which gets the
264 bytes back. Then if I bring up the blanker's window again the 264
bytes goes away again.
Did you run "avail flush" to see if the memory can be free'ed? Its not a
true memory leak unless it stays lost. But then using up 264 bytes more
each time you pop up the window is still not good.
Have you tried the C= commodities after a reboot when your commodity has
not been started? This would prove that your commodity is not involved in
the C= commodities losing memory.
I didn't find anything on this after looking through the past few months
of BIX messages. The number 264 shows up way too often, but mostly as a
message length. 😉
//
\X/ Amiga or bust! Gary Bonnstetter, Bonnsoft
I will have to go back and try again. I found some commodity code on the
DevCon disks and it was significantly different from what is in the RKMs
and AmigaMail.
I went on to other things and backburnered the commodity stuff for awhile
since it did "seem" to be working fine (aside from the memory problem).
>> I didn't find anything on this after looking through the past
>> few months of BIX messages.
Thanks for checking on that. I really appreciate your efforts. I dropped
my Bix account about 2 months back (after some 5 years) because it just
wasn't economical anymore, but I do miss the extra programming help i
could get there.
I'll let you know about the "avail flush" and the new"er" code I
installed. Thank you.
David Czaya …via AutoPilot
73445,407