I noticed that in the latest branch, when I visit the:
StrLib statistics Strings array size: 1758 <= it was only 160-250 before, rarely go about 500
Allocated strings: 80
Next slot to search: 944
0 1
I noticed that in the latest branch, when I visit the:
StrLib statistics Strings array size: 1758 <= it was only 160-250 before, rarely go about 500
Allocated strings: 80
Next slot to search: 944
I can confirm it's a bug, under heavy load, it changed to:
StrLib statistics
Strings array size: 7880
Allocated strings: 1256
Next slot to search: 559
and the engine hang
Other minor bug, in Modern theme, you forgot the 'ban' image
a.ban_link {
display: inline-block;
color: red;
font-weight: bold;
font-size: 24px;
text-decoration: none;
vertical-align: middle;
}
Very strange fault.txt
. Anyway, please update, it is very possible this bug is already fixed.
Hi johnfound
I updated to the latest 2.8 release in trunk, the 2 bugs below still existed, could you take a look ?
Strings array size: 32100
Allocated strings: 77
Next slot to search: 320
Other minor bug, in Modern theme, you forgot the 'ban' image
a.ban_link {
display: inline-block;
color: red;
font-weight: bold;
font-size: 24px;
text-decoration: none;
vertical-align: middle;
}
Thank you!
If you are considering a bug Strings array size: 32100
, it is not. This is simply indication that the engine has been loaded a lot and there were 32100 strings allocated in the past. But all they has been deleted. The current number of allocated strings is 77 which is OK for the normal work of the engine with one user browsing.
Well, this is actually funny. The point is that the function for banning users is still not implemented and not working. So this link (visible only for the admins is fake and not working). In Modern theme, there is no image, but Unicode character "thumb down" instead.
You can simply ignore this or delete the whole link from the template.
0 1