I am having a problem with the client growing into a monster that gobbles up a ton of available resources. When I first start it up, it will be under 100k but after a couple of days of running (if I forget to shut it down overnight) it can grow into a 400k+ monster. It has shut down on me a couple of times, complaining that it ran out of memory. Anybody else having this problem? I'm thinking there might be a memory leak somewhere...but not surprised with the amount functionality built in.

Any suggestions on how to lower consumption other than rebooting every day?


We're running VC in a MS Server 2003 R2 with Service Pack 2 environment.
It is running as a Virtual machine on a VMWare server.
It is emulating an E5410@2.33GHz with 1 Gig of RAM.

Do you have any special windows open - like log window or something - when it grows?

---

Dang you're good!!
The more related windows you have, the more resources it uses.
I guess I end up with a bunch of VC windows open at the end of the day.
I killed all the windows and it brought it back down under 100k.

Thanks a bunch!

Please write the Windows you have open here and we will look at memory usage for those. I know we currently not clear the log window so that could be a cause for the problem - which we probably need to fix for the future.

---

I checked the memory and it was at 77k.
I opened up the log, scrolled down to the bottom.
Minimized it and clicked on one of my tasks...it lagged a minute or so.
I checked the memory used with the log window open in the background...it's at 573k.

I'm attaching a screen print.

Yes, part of that memory will be thrown away (in garbage collection). You can try to minimize the windows (which will start a garbage collection). Real memory usage should not be 573k. Only allocated temporary. But, if you have it open for a longer time the real memory usage will be bigger.

---

hmm...
update.
I created a new job: memory=29k.
Double-Clicked on job : memory=97k
Clicked on 'task -> Add -> ftp': memory=111k.
Clicked on 'Add (for FTP/FTPS/SFTP)': memory=116k.
Clicked on 'Connections': memory=116k.
Clicked on 'Add -> FTP': memroy=650k.


I'm not creating 'new windows' just drilling down to the windows that I need to interact with.
In this case, I need to log into a new ftp server and retrieve files.
I did it several times and each time I ran through the process, it took memory usage up into the 620K-677K range. It lags alot when i'm using more than like 600K of real memory.

Must be something else then.

1. Do you have Jobs running very frequently?
2. what operative system?
3. 32 or 64 bit?

---

1. I currently have 9 jobs active. 3 are time-triggered, 2 are file-triggered. No jobs were firing off when I did my testing.

2. Microsoft Windows Server 2003 R2 operating system.

3. 32-bit.

I think I found out what the problem was with this.
I was remote loggining into the server running the VisualCron service and bringing up the VisualCron client there.

When I brought up the VisualCron client on my desktop which is running Windows 7 professional and connecting it to the service that was running on the VM server, I could not duplicate the memory problem . The most I was able to get the client to use was around 170K of real memory. That was by opening various log windows as well as drilling down into the windows of the various options. These activities were the ones causing problems before.

Consider this problem closed.

Thanks for all the feedback. We could not reproduce that memory usage either. We tried different operating systems and setups.

---

Just to follow up on this, Henrik.
We moved VisualCron to it's permanent home on a machine running Windows Server 2008 R2 with Service Pack 1.
This is a 64-bit operating system.
I also upgraded VisualCron to the 6.0.8 version.

I threw everything but the kitchen sink at it and it behaved beautifully. I am logging into it remotely and firing off the VisualCron client. I'm drilling through as many windows as I can and the memory used does not go above 170K.

Good work guys!!