Bug #3702
closedMonitor buffer logging is not always saved/restored correctly
0%
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
Updated by Per Amundsen over 7 years ago
What are the steps to reproduce making it save more than MAX lines?
Updated by Per Amundsen over 7 years ago
- Subject changed from Private Monitor buffer logging limit fail to Monitor buffer logging is not always saved/restored correctly
- Status changed from New to Resolved
I think I found the issue, but in case I didn't, I made it restore only MAX buffer on startup.
Updated by Mr. BS over 7 years ago
Good, at least it should load fine.
No clue how my client generated the big file, I just was away from irc for weeks, so updated to 3.0 beta yesterday and it was unable to startup properly.