In an app I'm developing, I have a log entry for every upgrade.

It says something like this:

Timestamp - "version old" - "version now" - "program comment (some thing
to summarize what's new in this version in one line)"

It sure would be beneficial now :p

 

Anyways, I will try to note everything down next time

 

________________________________

From: Thor S. 
Sent: 25. oktober 2008 23:42
To: '[email protected]'
Subject: RE: [taskcoach-dev] Bugs

 

Oops did not see the comments below.

The logfile is removed now. I see how it goes.

But it might not be taskcoach fault.

I did see a memory build up in my browser Opera at the same time,
however that might be a coincidence.

Thanks for the comments ;)

 

________________________________

From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Frank Niessink
Sent: 25. oktober 2008 21:10
To: [email protected]
Subject: Re: [taskcoach-dev] Bugs

 

Hi Thor,

Please always mention which version you are running. 'Version before
the latest release' is not specific enough unless we agree on what the
latest release is :-)

2008/10/25 Thor S. <[EMAIL PROTECTED] <mailto:thor918%40online.no> >:

> The task coach file had erased it self, showing 0KB. I'm not that
worried
> because this file is in my SVN-system, so it is backed up, however for
those
> that does not have a svn system, they would have lost everything. I
think I
> was running the version before the latest release. I did a new upgrade
now
> after the freezeup.

Probably something failed while saving, but I'm not sure.

> Another thing I see is in "C:\Program Files\TaskCoach"
>
> taskcoach.exe.log is 1.5 GB, is it suppose to grow that big?

All exceptions are logged. If an exception occurs every few seconds it
could get really big. Also, if you don't remove the taskcoach.exe.log
when you install a new version, it could contain very old data.

Please remove the taskcoach.exe.log now and when problems occur in the
future, open a bug report and attach both your TaskCoach.ini and the
taskcoach.exe.log file.

Thanks, Frank

 

Reply via email to