Hello, Can you determine if the delay is caused by Windows swapping in applications from disk to physical RAM memory for executing it on the CPU, resolving page faults, etc? Is the total memory of all currently running applications much larger than the physical RAM memory? We can look in a log file generated by Oxygen on your computer which will tell us if the delay occurs before or after the application resumes execution by receiving the CPU from the operating system (that is the delay is in the Oxygen application or in the operating system). For generating a log file please copy the attached file log4j.properties in the directory [Oxygen-install-dir]/lib, restart Oxygen, reproduce the delay, close Oxygen and send us all the files [Oxygen-install-dir]/oxygen.log* (that is oxygen.log, oxygen.log.1, oxygen.log.2, in case there is more than one log file). Regards, Sorin Seraphim Larsen wrote:

Hi all,

I'm a pretty new oXygen user (new since version 9.1). Really love the tool!

But one thing that is really annoying is that if I leave oXygen for awhile (say, 20 minutes), and then come back to it, it usually takes at least 20-30 seconds before it starts responding, and it can sometimes take several minutes. I guess it's some kind of memory paging issue or something. This sometimes happens with other programs too, but it's much worse with oXygen than with any other program that I use.

Is there something I can do to configure oXygen to get rid of this problem?

I'm running oXygen 9.2 on Windows XP.

Thanks, Seraphim

log4j.rootCategory= debug, R2 # R2 will write log to file log4j.appender.R2=org.apache.log4j.RollingFileAppender log4j.appender.R2.File=oxygen.log log4j.appender.R2.MaxFileSize=12000KB log4j.appender.R2.MaxBackupIndex=4 log4j.appender.R2.layout=org.apache.log4j.PatternLayout log4j.appender.R2.layout.ConversionPattern=%r %p [ %t ] %c - %m%n