Hi I have seen fluctuations on JFW memory useage here as well. I've seen JFW using anywhere from 25 megs to 45 megs of memory and the size does tend to increase as the application is running in memory but version 9 seems to be much less of a memory leaker than previous versions. Running Jaws 9 here on both XP and Vista. Rick -- Visit my webpage and podcast feed at: http://www.blind-geek-zone.net and my web Blog at: http://blind-geek-zone.blogspot.com/ Join the BGZ mailing list by sending a blank email message to: blind_geek_zone-request@xxxxxxxxxxxxx and put subscribe in the subject line. ----- Original Message ----- From: Brian Hansen To: jfw@xxxxxxxxxxxxx Sent: Sunday, October 07, 2007 12:04 AM Subject: Re: JFW 9 Beta Memory Issues HMMM! Now that's really strange. Maybe it's time to start listing out our hardware, and what flavor of XP we're using. Win XP Home SP2 2GB of memory my system is setup to not have a swap file on the primary HD. Pentium 3.4GHz. Dual Core processor Asus motherboard with the Intel 975X chipset NVidia GForce 6600GT video card with 128MB of memory 2 SATA HD's Maybe this can start shedding some light on things. Blessings, Brian ----- Original Message ----- From: Agent86b To: jfw@xxxxxxxxxxxxx Sent: Saturday, October 06, 2007 6:53 PM Subject: Re: JFW 9 Beta Memory Issues Brian, I am using Win XP and do not see this problem either. However I will keep checking from time to time. Max. on 09:47 7/10/2007, Brian Hansen said: Not too techie at all. I wonder if since you're using Vista at this point, if it isn't a XP issue since you're not seeing the growth changing. Blessings, Brian ----- Original Message ----- From: "Joseph Lee" <joseph.lee22590@xxxxxxxxx> To: <jfw@xxxxxxxxxxxxx> Sent: Friday, October 05, 2007 11:05 PM Subject: re: JFW 9 Beta Memory Issues Hi Brian, This kind of thing is called memory leak--a condition where the application executable fails to release memory that it no longer needs. From my testing, it seems that it does not occur to me. The process of obtaining and releasing memory is normal behavior for applications. This is because of the following two reasons: a. If an application is composed of threads--a small application code--of execution (known simply as thread), then it is natural for the process to use more memory than expected. More threads within the executable translates to more memory usage. Contrary to people's belief, JAWS is composed not only of just one thread, but multiple threads as well. The jfw executable consists of JAWS tracking engine which gathers information on the screen, synthesizer controller that relays information gathered from tracking engine and sends it to speech synthesizer such as Eloquence, and braille display unit which relays information on the screen and translates to braille characters (this works properly when a braille display such as PAC Mate Portable is attached). JAWS also includes Virtual Buffer which is activated when applications that require virtual cursor is running, such as Internet Explorer and Anobe Reader. The application you run, the more tracking routine is needed, consequently leading to more memory usage. And once the thread is no longer needed, jfw releases memory associated with the thread. b. If an application needs to access cevices and software modules such as USB devices and drivers, it needs more memory to load device drivers and/or software modules. In order for JAWS to run properly, it requires Mirror Display Driver. The initial memory usage of jfw, coupled with device driver for Mirror driver results in more memory usage than expected. Hope it was not that "too techie" for you. If you want simpler explanations, let me know. Cheers, Joseph P.S.Tested using Windows Vista and JAWS 9.0.353. ----- Original Message ----- From: "Brian Hansen" <bc.hansen23@xxxxxxxxx To: <jfw@xxxxxxxxxxxxx Date sent: Sat, 6 Oct 2007 16:20:06 -0500 Subject: JFW 9 Beta Memory Issues Please forgive me if this has been recently discussed, but I just now got back on the list. Have any of you noticed that even when the screen isn't changing, JFW 9 Beta is continuing to grow in memory? If you go into the "Task Manager" using CTRL-ALT-DEL, and go to the "Services" tab, hit the letter "j" until you get to JFW, you'll get the amount of memory JFW is currently using. Now if you hit F5 to refresh your screen you'll find that the amount of memory is continuing to grow. The amount that it increases seems to be relevant to the amount of time you let pass before hitting the Refresh command. If nothing but the memory usage is changing on the screen, why is it growing in such chunks, and why is the amount of time one waits effecting the size of the memory growth? Blessings, Brian -- JFW related links: JFW homepage: http://www.freedomscientific.com/ Scripting mailing list: http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com JFW List instructions: To post a message to the list, send it to jfw@xxxxxxxxxxxxx To unsubscribe from this mailing list, send a message to jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. Archives located at: //www.freelists.org/archives/jfw If you have any concerns about the list, post received from the list, or the way the list is being run, do not post them to the list. Rather contact the list owner at jfw-admins@xxxxxxxxxxxxxx -- JFW related links: JFW homepage: http://www.freedomscientific.com/ Scripting mailing list: http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com JFW List instructions: To post a message to the list, send it to jfw@xxxxxxxxxxxxx To unsubscribe from this mailing list, send a message to jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. Archives located at: //www.freelists.org/archives/jfw If you have any concerns about the list, post received from the list, or the way the list is being run, do not post them to the list. Rather contact the list owner at jfw-admins@xxxxxxxxxxxxxx