batterybar pro log 20+ gigs

[ctkatz]

i was wondering, is the log file for battery bar known to get up to fairly large sizes? if not, this may be a pretty major bug.

this is a 3.3.0 beta version and i didn't see anything about an out of control log file anywhere here.

[Chris]

I found a bug in BatteryBar that's causing that issue. Essentially, it's logging the same error over and over again. If you have an outbound firewall blocking access that could be causing the problem.

You are free to delete the log file.

The next version (3.3.2) will include the fix for the issue and will also feature a log-limiter that will not allow the log to grow over about 5MB.

[Guest]

was about to report it, too

Didnt notice it until my hdd was half full :x

my log was 55 gb big

just writeprotected the file now

thx for already fixing this issue, chris

[Ashkan]

I know this limit has changed since 3.3.2, what is the current limit? I thought it was 30mb but after 3.4.5 beta 3 I have a log of 36.3mb

[Chris]

The log file size limit is 3MB (x2). When the log file reaches 3MB in size, it renames it to .log.old and then creates a new log file. So the log files should never get larger than 6MB total old+new.

I suppose it's possible that if you had an old log file that was larger than the limit and the software created a new log file, but the new log file never reached the 3MB limit that it would leave the old log in place and not delete it since the .log.old file gets deleted only when the .log file reaches 3MB.

Also, the filesize is checked only on startup and whenever an exception is logged, so if you have regular DEBUG logging turned on, it won't cut off the log (to allow for situations in which a detailed log is necessary) until the next time the start is started (Windows startup).

You can safely delete the log, or you can use the Send Feedback feature which will automatically compress the log and upload it and then delete it afterwards.

[Ashkan]

(02-07-2011 05:06 PM)Chris Wrote:  The log file size limit is 3MB (x2). When the log file reaches 3MB in size, it renames it to .log.old and then creates a new log file. So the log files should never get larger than 6MB total old+new.

I suppose it's possible that if you had an old log file that was larger than the limit and the software created a new log file, but the new log file never reached the 3MB limit that it would leave the old log in place and not delete it since the .log.old file gets deleted only when the .log file reaches 3MB.

Also, the filesize is checked only on startup and whenever an exception is logged, so if you have regular DEBUG logging turned on, it won't cut off the log (to allow for situations in which a detailed log is necessary) until the next time the start is started (Windows startup).

You can safely delete the log, or you can use the Send Feedback feature which will automatically compress the log and upload it and then delete it afterwards.

I've never seen it create a .log.old file. I don't reboot that often and checking the settings.xml enable debug logging is set to false and log battery status is set to true.

   

[Chris]

Are you running BatteryBar 3.4.4 or some older version?

Also, the log file shows it was modified as recently as today. You may want to check and see what errors are being logged.

[Ashkan]

I am using 3.4.5 beta 3.