Slow loading when filtering is enabled on startup

[Former user]

Hi Ondrej!

I use your program to simplify TXT log files. I like it, however would like to propose some better features and to report some possible bugs.

1. It would be nice to have a shortcut button for managing parser settings.
2. This may be a bug: when I forget to uncheck one of the shortcut buttons (or both) of enable/disable filters and/or colors, before closing the program, then after startup, at next file open it lasts very long (several minutes) to open the file. In the lower pane window I can see as it processes the lines one by one, which takes very long time. What's more - it goes through the whole file several times, again and again. I use XP prof SP3. Answer me here for more info.

Thanks for your attention and efforts! Tivadar

[Ondrej Salplachta]

Hi Tivadar, thanks a lot for your feedback! I'm really glad you like my tool.

As for the shortcut key I've created issue #4 - feature request and it will be included in upcoming version.

About the bug: It's interesting since in version 6.5.2 isn't saved state of check button for enabling filters - it's always unchecked when application starts.

Please could yo send me debug logs from the ALV?: 1.Set debug log level for the ALV (Edit AdvancedLogViewer.exe.config and on line#25 set <level value="INFO" /> to <level value="DEBUG" />) 2. Delete all the files in "c:\Users\All Users\Application Data\AdvancedLogViewer\Logs" 3. Then repeat the steps you mentioned 4. Send me all the logs in folder mentioned in step#3

I'll try to figure out what could be wrong from the logs.

Thanks for cooperation!

Ondrej

[Tivadar Kecskes]

Hi, Ondrej!

Thanks for paying attention to my report!

I uploaded the requested report files and some screenshots, too. The last LOG (AdvancedLogViewer_[2404].log) e.g. was created, when a ca. 2MB log-file lasted to open from 12:19:15-12:19:45.

Much success for debugging! Tivadar

[Tivadar Kecskes]

and the LOG-s

[Ondrej Salplachta]

I see where the issue is, it's caused by wrongly configured parser which thinks that all log is one row instead of separate rows. And thus all the text is shown in the bottom window instead of separate rows in the main window.

Please add new pattern with following definition: {Date} {Time}.{Time}:{Message} and name which matches your log names (if you don't use ALV for another log format, just name it *).

The reason why is it so slow with enabled color highlighting is the fact that all text is shown in the bottom box and ALV tries to colorize all this text instead of colorize just rows shown in the main window.

Here is an example how the log should looks like with correctly set parser: https://bitbucket.org/osalplachta/advanced-log-viewer/issue-attachment/3/osalplachta/advanced-log-viewer/1357225698.32/3/TestLogCorrectParser.png

Please let me know if it helps or you need any help with setting the parser.

Thanks, Ondrej

[Tivadar Kecskes]

Hi Ondrej!

Thanks for the advice! I tried this pattern for the parser, but the symptom did not change. (The view was at least beautiful.) I upload some new screens with additional info, and the sample log, too. Perhaps it helps to catch the problem. I suppose (just guess) this is may not be because of the parser, because this appears before I would really make any choice of pattern. I also attached a sample log for you to test with.

Another possible bugs: - I used for this test the latest version. I installed .NET4 and upgraded ALV. At first running everything became very slow for ca 1 minutes. Later it was OK.

-Once, when I wanted to change an already chosen parser, It gave an error message about a wrong exception.

Much success! Tivadar

[Ondrej Salplachta]

Hi Tivadar, thanks a lot for detail information, it allowed me to find root cause of the issue. The problem is that ALV is designed to open log with pattern by it's name - it means that pattern name should match to the file name. So when the log is opened and wrong parser is applied (the generic one) then whole log is loaded as one line. Then the correct parser is selected later -> there is a bug -> whole log is loaded in the detail window and it's slow. So I'll fix this in next version (should be within one week).

Expected behavior after the fix: When some log is opened and wrong parser is used (whole log is loaded as one line), nothing is shown and dialog with pattern selection is shown. So shouldn't happen that whole log is loaded as one item.

Another issue with parsing date: It's also a bug in the ALV and I need to figure out how to fix. In mean time, please use following pattern: {Date}.{Time} - {Type} {Message} and following date time format: yyyy MM.dd.HH:mm:ss.fff

This works and correctly parse date time in the log. The problem is in period character between date and time, so as a date is parsed just year and thus it's represented as '[year] [rest of datetime]'. It's a bug.

About he .NET4 It's interesting, I guess it's because of loading .NET assemblies for first time. But I'll try on fresh machine to be sure there is no issue with .NET 4 in general.

Please let me know if the pattern works for you and I'll update this case immediately when new version with the fix is out.

Thanks, Ondrej

[Ondrej Salplachta]

Actually I decided to fix issue with the parser immediately, so it's fixed in version 7.0.2. Please let me know if it fixes your issue with slow loading when color highlighting is selected.

Thanks, Ondrej

[Tivadar Kecskes]

Hi Ondrej!

I tested the new version. It works! It's fine!

The files open fast, and it immediately requests to chose the matching parser. Then it correctly parses. I tried the Time / date format you suggested, and it is also OK.

Thanks for your attention and efforts! Have much success in further jobs, too! Tivadar

[Ondrej Salplachta]

Great, I'm glad to hear that! :-) Thanks a lot for your feedback and cooperation, have fun with the ALV! ;-)

Ondrej

[Ondrej Salplachta]

Fixed in version 7.0.2