[GALAXY]

Hi
For several weeks I have the problem that my Cs 1.6 server crashes.

Here is the error message

L 03/04/2014 - 19:13:51: [AMXX] Run time error 4 (plugin "hlstatsx_commands_cstrike.amxx") - debug not enabled!
L 03/04/2014 - 19:13:51: [AMXX] To enable debug mode, add "debug" after the plugin name (without quotes) in plugins.ini.
L 03/04/2014 - 19:13:51: FATAL ERROR (shutting down): New message started When msg '86 'has not been sent yet
FATAL ERROR (shutting down): New message started When msg '86 'has not been sent yet

I have no explanation for it.
Perhaps I can help a. Post Wanted in the German forum but that's all no more unfortunately.
greetings

[YamiKaitou]

Enable debug as the message states. Then post the new error

[Xongie]

Hello,

I´ve got the same error on a CS 1.6 server.
With debug enabled I get following message:

L 03/11/2014 - 13:05:59: [AMXX] Displaying debug trace (plugin "hlstatsx_commands_cstrike.amxx") L 03/11/2014 - 13:05:59: [AMXX] Run time error 4: index out of bounds L 03/11/2014 - 13:05:59: [AMXX] [0] hlstatsx_commands_cstrike.sma::psay (line 627) L 03/11/2014 - 13:05:59: [AMXX] [1] hlstatsx_commands_cstrike.sma::hlx_amx_bulkps ay (line 685) L 03/11/2014 - 13:05:59: FATAL ERROR (shutting down): New message started when msg '86' has not been sent yet FATAL ERROR (shutting down): New message started when msg '86' has not been sent yet

I use version 1.6.19 (HL1).
If you need further information just let me know.

Thanks for your help.

Kind regrads,
Robert

[YamiKaitou]

You are missing a line of the error message, there should be 1 before what you show

[Perlendieb]

cancle.

[Xongie]

Hi and thanks for your help!

Originally Posted by YamiKaitou You are missing a line of the error message, there should be 1 before what you show

No, that´s all. What makes you think, there are more error lines regarding this problem?

As far as I can debug this problem, this seems to be a real bug.
Apparently, the code makes it possbile that a message wants to be written while another one is still being processed.

The only thing I am wondering about is, that there are always the same lines involved. There are other messages being sent which do not cause the problem (yet).

[YamiKaitou]

Originally Posted by Xongie No, that´s all. What makes you think, there are more error lines regarding this problem?

Because there almost always is the actual error message before the stack trace. I'll take a look when I get the chance to see if I see something

[YamiKaitou]

Are you guys able to reproduce this error with ease? If I was to create a debugged version, would somebody be willing to install it and reproduce the error?

[Xongie]

Hi!

Originally Posted by YamiKaitou Are you guys able to reproduce this error with ease? If I was to create a debugged version, would somebody be willing to install it and reproduce the error?

We would like to help by installing a debug version of the plugin.

So far we were not able to reproduce the error. Today some people could play without any issues for 3 to 4 hours.

It seems the error comes only into effect randomly.

[YamiKaitou]

Originally Posted by YamiKaitou If I was to create a debugged version, would somebody be willing to install it and reproduce the error?

Sorry for continously forgetting, but attached is the promised debugged version. It will create a file called psay_86.log, just attach that file once you notice a crash

Originally Posted by Krillin We get this problem since we installed HLStatsX:CE on our CSS and CS:GO server.

Then you have a different problem as this crash is specific to GoldSrc

Originally Posted by Krillin So it is not just related to Stable or DEV Builds of AMXMOD-X. You should not be using a DEV build to report this problem. The stable version is 1.8.2. So this particular problem should not have even been posted to begin with?

There is nothing wrong with 1.8.3 and bugs should always be reported.

Originally Posted by Krillin Right now we are on a DEV build with Source MOD so we are not reporting any problems until the newest STABLE build is out and running, re-compiled and running. They got broken this past week with the updates.

If you don't report problems now, then you will continue to encounter them later. Wouldn't you rather them fixed before the next release?