Wow interesting, at the time of this message my wineyes process in task
manager is showing as 300,704 K.
Cory
On 22/06/2011 4:43 PM, Ralf Kefferpuetz wrote:
Well, running WE about 19 hours and WE takes 129kb.
Nothing I would complain.
Ralf Kefferpuetz
Germany
-----Original Message-----
From: Cory Martin [mailto:[email protected]]
Sent: Thursday, June 23, 2011 12:17 AM
To: [email protected]
Subject: Re: Memory Issue
Hmmm yes I'm seeing this as well. I can track it over a day or so
and see how much it increases, but a couple hours ago it was using
roughly 250mb and now I just checked and it's using 302mb or there
abouts. That is a fair amount of RAM for it to be eating up isn't it?
I know a screen reader is a complex program though, but is there a way
to control that sort of issue? Or is just restarting the program the
only solution for the time being? Fortunately it doesn't seem to be
slowing down at all as a result, but yes definitely I think this needs
to be addressed.
Cory
On 22/06/2011 2:06 AM, Andrea Sherry wrote:
Using Windows 7 Home Premium 64-bit.
Using WE7.5.1.
Have noticed that Wineyes still devours memory over time and wonder if
anyone has encountered this issue.
Cheers
Andrea
If you reply to this message it will be delivered to the original sender
only. If your reply would benefit others on the list and your message is
related to GW Micro, then please consider sending your message to
[email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can
manage your list subscription at http://www.gwmicro.com/listserv.
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
