You guys really need to look into memory leakage problems in your client. My client crashes at least 3 times a day. I can cause it to crash by just going down my 40 or so jobs, opening each one, changing the job name and closing the job. If I go down the line I can get through all of them, but it will crash before I go through it a second time.
It seems that the more windows I drill through within the jobs and make changes, the slower the client gets, the more resources it consumes and eventually, it crashes.
It's very annoying.

This has happened on the following machine:
-a workstation running Windows 7, with 2 Gigs of ram.
-a server Running Windows Server 2008 with 8 gigs of ram.
-a a server running Windows Server 2003 with 4 Gigs of ram.

It has happened since version 5.0.8, all the way to the current one, 6.1.4.
It is even worse if you are running the client on the server as opposed to running the client on a workstation and connecting to the server.

Hi,

did you upgrade yesterday to final version?

How does it crash - do you get the popup from VisualCron (so you send the error report) or does the window just vanish?

How much memory does it use when it crashes (approximately).

Are you running Jobs very frequently?

Do you have the Client open overnight or do you close it when you are complete?

---

I'm using 6.1.4 as of a couple of weeks ago.
I get the pop-up when it crashes asking if I want to restart VisualCron.
Sometimes, I get a bunch of red 'X''s across the active windows, when I close those I keep getting red 'X's across the remaining windows, then it shuts down.
It uses upwards of 570k of executable memory when it gets to the point of crashing.
I don't have to be running jobs for it to crash, but the test system I am doing this only has around 10 active jobs, with about 30 inactive.
I reboot my machine overnight, then turn it on in the morning. I get my first VC client crash within a couple of hours of opening and closing job windows. So from a fresh reboot, VC will crash when I open and close windows like I explained on my original post.

Ok, thanks for the info.

So, first, there is one unhandled crash fix in latest version so please re-install because you are probably using an early beta.

Could you send a typical daily log to support@visualcron@com. I am thinking about the log_serverDATE.txt. This would help determine what kind of activity and how much.

---

Hi,

please test the latest 6.1.5 as we have fixed some memory leaks there:

http://www.visualcron.co....aspx?g=posts&t=2743 

---