SA-MP Forums Archive
Stack/Heap Collision - Complications - Printable Version

+- SA-MP Forums Archive (https://sampforum.blast.hk)
+-- Forum: SA-MP Scripting and Plugins (https://sampforum.blast.hk/forumdisplay.php?fid=8)
+--- Forum: Scripting Help (https://sampforum.blast.hk/forumdisplay.php?fid=12)
+--- Thread: Stack/Heap Collision - Complications (/showthread.php?tid=588270)


Stack/Heap Collision - Complications - Kyle - 07.09.2015

I'm having a little trouble with the script at the moment, I've been looking over my console log and noticed a few errors.

The sole error being this:

Код:
Run time error 3: "Stack/heap collision (insufficient stack size)"
Stack pointer (STK) is 0xB3B5C8, heap pointer (HEA) is 0xB3B5B0
There is an AMX backtrace of the following functions

Код:
- ShowInventory
- PickRandomSkill
- HideBox
- ShowTextdrawInfoBox
I've noticed that they're all linked, A random skill is picked, HideBox is called, ShowTextdrawInfoBox is called then once that's been called ShowInventory will be called.

I've been told I can increase the pragma dynamic size to see if that addresses it, I've tried that and it doesn't work.
Currently it's on this: #pragma dynamic 30000000

If I compile without any flags there's no warning messages about stack size either.

I've also noticed on one occasion after a server GMX it only took 34 minutes for it to occur. Within that time nobody connected apart from the bots and 2 players at the 29th minute who performed no commands and another player at the 32nd minute.

Four seconds after player 2 joined, it occured.

On example 2 it happened after 2 hours, 14 minutes and 26 seconds. 2 players joined within that time, 1 player at 1:30hr and quit at 1:32 and player 2 at 2:12 with the stack issue at 2 hrs 14.

I've also noticed that sometimes it'll spam the AMX backtrace, stop for a second or two, let some stuff occur such as a connection or login and then repeat the Stack Overflow error.

I've also noticed that the AMX Backtrace Functions aren't the ones actually being called.

Like this for example:



I've also noticed it can error / warn for ages and then suddenly out of the blue stop:



If somebody could assist me I would highly appreciate it.

Re: Stack/Heap Collision - Complications - JernejL - 07.09.2015

Perhaps a infinite recursion loop in script? looks like your call stack goes over 100 deep, that might be too much for pawn, there is a chance you have large non-static arrays in those subroutines and they exhaust your stack.. check it out