1. [winlib] Possible Massive Resource Leak in 0.57.6
--=====================_1490383==_.ALT
Hello All!
I believe that I have found a massive resource leak in -- one that I
thought that Derek had fixed in version (and probably that he thought he
fixed too 
). The only thing is that I would like to get confirmation
of it from someone else. The pickle here is that it has been found not to
occur on XP, whose memory resource works are apparently much different than
Windows ME, which I happen to be using.
So, I am hoping I could get someone with Windows ME to confirm this
problem. To do that, you'll need the following:
1. winlib32 version 0.57.6
2. My "ruler.zip" file (found in the Euphoria archives)
3. Windows ME
4. Be VERY prepared to reboot after you do this!!
Unzip the ruler file, and execute play.exw. Take the ruler out of its
holder, then right-click and select "Span across screen." At this point on
my machine, the memory leak really begins to show up. I've been using
System Resources to observe this. With 293M of memory, it takes me about
15 seconds to bottom out.
If someone could confirm this for me, it would be appreciated. I don't
want to waste Derek's time.
Thank you,
Travis Beaty
Evans, Colorado.
--=====================_1490383==_.ALT
Content-Type: text/html; charset="us-ascii"
<html>
Hello All!<br>
<br>
I believe that I have found a massive resource leak in -- one that I
thought that Derek had fixed in version (and probably that <i>he</i>
thought he fixed too ). The only thing is that I would like to
get confirmation of it from someone else. The pickle here is that
it has been found <b>not</b> to occur on XP, whose memory resource works
are apparently much different than Windows ME, which I happen to be
using.<br>
<br>
So, I am hoping I could get someone with Windows ME to confirm this
problem. To do that, you'll need the following:<br>
<br>
1. winlib32 version 0.57.6<br>
2. My "ruler.zip" file (found in the Euphoria
archives)<br>
3. Windows ME<br>
4. Be <b><u>VERY</u></b> prepared to reboot after you do
this!!<br>
<br>
Unzip the ruler file, and execute play.exw. Take the ruler out of
its holder, then right-click and select "Span across
screen." At this point on my machine, the memory leak really
begins to show up. I've been using System Resources to observe
this. With 293M of memory, it takes me about 15 seconds to bottom
out.<br>
<br>
If someone could confirm this for me, it would be appreciated. I
don't want to waste Derek's time.<br>
<br>
Thank you,<br>
<br>
Travis Beaty<br>
--=====================_1490383==_.ALT--
2. Re: [winlib] Possible Massive Resource Leak in 0.57.6
Hi Travis,
I have Win ME so i replicated your bug. It doesn't seems to me to be
a memory bug but a processor one.. I've a program that shows memory
info and it's didn't show an increment, but i heard my disk reading as
hell and i think that my processor was to loaded because all what i
tried to do was slow... Finally after ctrl+alt+del and closing the app
everything came back to normallity...
It's a bug.. but i don't think that's memory related..
Best Regards,
Guillermo Bonvehi
--- Travis Beaty <travis_beaty at mcleodusa.net> wrote:
>
> Hello All!
>
> I believe that I have found a massive resource leak in -- one that I
> thought that Derek had fixed in version (and probably that he thought
> he
> fixed too ). The only thing is that I would like to get
> confirmation
> of it from someone else. The pickle here is that it has been found
> not to
> occur on XP, whose memory resource works are apparently much
> different than
> Windows ME, which I happen to be using.
>
> So, I am hoping I could get someone with Windows ME to confirm this
> problem. To do that, you'll need the following:
>
> 1. winlib32 version 0.57.6
> 2. My "ruler.zip" file (found in the Euphoria archives)
> 3. Windows ME
> 4. Be VERY prepared to reboot after you do this!!
>
> Unzip the ruler file, and execute play.exw. Take the ruler out of
> its
> holder, then right-click and select "Span across screen." At this
> point on
> my machine, the memory leak really begins to show up. I've been
> using
> System Resources to observe this. With 293M of memory, it takes me
> about
> 15 seconds to bottom out.
>
> If someone could confirm this for me, it would be appreciated. I
> don't
> want to waste Derek's time.
>
> Thank you,
>
> Travis Beaty
> Evans, Colorado.
3. Re: [winlib] Possible Massive Resource Leak in 0.57.6
On 26 May 2002, at 11:44, pampeano at rocketmail.com wrote:
>
> Hi Travis,
> I have Win ME so i replicated your bug. It doesn't seems to me to be
> a memory bug but a processor one.. I've a program that shows memory
> info and it's didn't show an increment, but i heard my disk reading as
> hell and i think that my processor was to loaded because all what i
> tried to do was slow... Finally after ctrl+alt+del and closing the app
> everything came back to normallity...
> It's a bug.. but i don't think that's memory related..
That's memory related. The disk thrashing was the virtual memory
manager using the harddrive because ram was full.
Kat
> Best Regards,
> Guillermo Bonvehi
>
> --- Travis Beaty <travis_beaty at mcleodusa.net> wrote:
> >
> > Hello All!
> >
> > I believe that I have found a massive resource leak in -- one that I
> > thought that Derek had fixed in version (and probably that he thought
> > he
> > fixed too ). The only thing is that I would like to get
> > confirmation
> > of it from someone else. The pickle here is that it has been found
> > not to
> > occur on XP, whose memory resource works are apparently much
> > different than
> > Windows ME, which I happen to be using.
> >
> > So, I am hoping I could get someone with Windows ME to confirm this
> > problem. To do that, you'll need the following:
> >
> > 1. winlib32 version 0.57.6
> > 2. My "ruler.zip" file (found in the Euphoria archives)
> > 3. Windows ME
> > 4. Be VERY prepared to reboot after you do this!!
> >
> > Unzip the ruler file, and execute play.exw. Take the ruler out of
> > its
> > holder, then right-click and select "Span across screen." At this
> > point on
> > my machine, the memory leak really begins to show up. I've been
> > using
> > System Resources to observe this. With 293M of memory, it takes me
> > about
> > 15 seconds to bottom out.
> >
> > If someone could confirm this for me, it would be appreciated. I
> > don't
> > want to waste Derek's time.
> >
> > Thank you,
> >
> > Travis Beaty
> > Evans, Colorado.
>
>
>
>
