Version 4.19.4 works fine, but all versions since 4.20 cause a crash in some situations.
Tested on both CentOS and Ubuntu, on vanilla SA-MP server R2 and R3 just with plugins crashdetect.so PawnPlus.so. Not affected by long_call_time 0. Crashlog is sometimes produced, sometimes not:
This point of crash is somewhere before the banlist is loaded (otherwise it would show in log). One possibility points to the fopen hook, which is used in PawnPlus to load debug info from the AMX. There is a crashdetect-specific code in PP that essentially moves the hook one level up in case crashdetect hooks it already.
I can confirm that without the fopen hook in PawnPlus, the server launches fine, but I am not sure what causes the issue. It was also reported that moving to Debian or adding other plugins prevented the crash, but that might be just random behaviour.
Version 4.19.4 works fine, but all versions since 4.20 cause a crash in some situations.
Tested on both CentOS and Ubuntu, on vanilla SA-MP server R2 and R3 just with
plugins crashdetect.so PawnPlus.so
. Not affected bylong_call_time 0
. Crashlog is sometimes produced, sometimes not:This point of crash is somewhere before the banlist is loaded (otherwise it would show in log). One possibility points to the
fopen
hook, which is used in PawnPlus to load debug info from the AMX. There is a crashdetect-specific code in PP that essentially moves the hook one level up in case crashdetect hooks it already.I can confirm that without the
fopen
hook in PawnPlus, the server launches fine, but I am not sure what causes the issue. It was also reported that moving to Debian or adding other plugins prevented the crash, but that might be just random behaviour.