Project

General

Profile

Actions

Bug #3702

closed

Monitor buffer logging is not always saved/restored correctly

Added by Mr. BS over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Interface
Target version:
Start date:
08/29/2017
Due date:
% Done:

0%

Estimated time:
Operative System:
All
Regression:
No

Description

Bellow is my current Monitor Panels config:

[Monitor]
EnableMonitor=True¦True¦True¦True¦True¦True
MonitorBuffer=200¦200¦200¦200¦200¦200
MonitorExclude=*nickserv,*sasl,*status,#GRfanfic,#sdasdas,#blabla,#beast-xdcc,
MonitorInclude=
MonitorServerNickcolumn=False
MonitorServerTimestamp=True
MonitorServerNetwork=True
MonitorChannelNickcolumn=False
MonitorChannelTimestamp=True
MonitorChannelNetwork=True
MonitorIgnoreDuplicates=True
MonitorExcludeActive=True
MonitorShowMessages=0
MonitorShowEvents=0¦0¦0¦0¦0¦0¦0¦0
MonitorSave=True¦False¦True¦True

For some unknown reason, AdiIRC was able to save a huge 116 MB Private buffer on my end full of repeated garbage messages. Due this big log file, the client crash or stay in some loop on startup I guess, maybe waiting a long time it could be able to load it, I'm not in mood to wait that long :P

If you want to give it a try, log file is attached. Extract it to Cache\Monitor folder and use my config above.

I thought setting buffer to 200, the log file would have only 200 entries.

Tested on latest fresh beta build, as always.


Files

private monitor.zip (424 KB) private monitor.zip Mr. BS, 08/29/2017 11:50 PM
Actions

Also available in: Atom PDF