You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Program freezes. This happens not every time, due to a random insert order.
Expected behavior
Program finishes and statistic is updated.
Screenshots
Not applicable.
Desktop (please complete the following information):
OS: Windows Server 2022 (21H2/20348.2402)
Perl: StrawberryPerl 5.38.2.2 (x64)
Version: 7.9
Additional context
I already analyzed the problem and fixed it for me. The error happens, because awstats detects a search keyword with the value 0. If another keyword has the same number of instances, the check for existance of this key in AddInTree fails and the value is inserted. After that, the nextval hash has an entry with the same value for key and value. If a subsequent insert tries to find the correct position, we are stuck in an infinite loop.
My fix on line 8369 is just using exists for the check, if a key exists.
if ( exists$val{$keyval} ) { # Val is already in tree
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
awstats.pl -config=demo -update -LogFile="demo.log"
Expected behavior
Program finishes and statistic is updated.
Screenshots
Not applicable.
Desktop (please complete the following information):
Additional context
I already analyzed the problem and fixed it for me. The error happens, because awstats detects a search keyword with the value 0. If another keyword has the same number of instances, the check for existance of this key in
AddInTree
fails and the value is inserted. After that, thenextval
hash has an entry with the same value for key and value. If a subsequent insert tries to find the correct position, we are stuck in an infinite loop.My fix on line 8369 is just using exists for the check, if a key exists.
The text was updated successfully, but these errors were encountered: