'bad allocation' errors

taxman · **Joined:** Tue Apr 18, 2006 11:10 pm **Posts:** 44

POL097-2008-02-26 Coregina (VS.NET 2003)
compiled on Feb 26 2008 22:16:06

After ~60 hours of uptime have this:

Code:

[03/08 23:38:56] Exception in: scripts/ai/killPCs.eclze() doesn't take parameters.: bad allocation
 PC < nLines: (ndex) requires a parameter.unsigned1399:  1399: get member id 'z' (2)
  1400: global #3
  1401: get member id 'realm' (113)
  1402: 1L
  1403: 7L
  1404: Func(4,28): FindPath
>1405: local2 := 
  1406: local #2
  1407: 1L
  1408: [] 1
  1409: get member id 'x' (0)
Exception in: scripts/ai/killPCs.eclze() doesn't take parameters.: bad allocation
 PC < nLines: (ndex) requires a parameter.unsigned1399:  1399: get member id 'z' (2)
  1400: global #3
  1401: get member id 'realm' (113)
  1402: 1L
  1403: 7L
  1404: Func(4,28): FindPath
>1405: local2 := 
  1406: local #2
  1407: 1L
  1408: [] 1
  1409: get member id 'x' (0)
Exception in: scripts/ai/spellKillPCs.ecle: bad allocation
 PC < nLines: (orted2061:  2061: get member id 'z' (2)
  2062: global #7
  2063: get member id 'realm' (113)
  2064: 1L
  2065: 7L
  2066: Func(4,40): FindPath
>2067: local2 := 
  2068: local #2
  2069: 1L
  2070: [] 1
  2071: get member id 'x' (0)
Exception in: scripts/ai/spellKillPCs.ecle: bad allocation
 PC < nLines: (orted2061:  2061: get member id 'z' (2)
  2062: global #7
  2063: get member id 'realm' (113)
  2064: 1L
  2065: 7L
  2066: Func(4,40): FindPath
>2067: local2 := 
  2068: local #2
  2069: 1L
  2070: [] 1
  2071: get member id 'x' (0)

Seems 097 gives more information. I hope this can help to locate error and to fix it. If neede more info or something - tell me.

CWO · **Posted:** Tue Mar 11, 2008 5:19 am

Seems something with getting the Z parameter on or before FindPath?

taxman · **Joined:** Tue Apr 18, 2006 11:10 pm **Posts:** 44

It is symptom, not reason.

Now, after ~55 hours i see the same: 'bad allocation' errors and 'zombie' connections.

Code:

Waiting for 161 child threads to exit
Waiting for 161 child threads to exit
Waiting for 161 child threads to exit
Waiting for 161 child threads to exit
Waiting for 161 child threads to exit
Waiting for 161 child threads to exit
No clock movement in 30 seconds.  Dumping thread status.
*Thread Info*
Semaphore PID: 0
Scripts Thread Checkpoint: 53
Last Script: scripts/misc/logoff.ecl PC: 207
Escript Instruction Cycles: 48606999212
Tasks Thread Checkpoint: 9
Active Client Thread Checkpoint: 116
Current Threads:
660 - Main
1104 - ThreadStatus
Waiting for 161 child threads to exit

POL waiting for 161 threads that not exists.

coltain · **Posted:** Sun May 04, 2008 10:28 am

any progress??

taxman · **Joined:** Tue Apr 18, 2006 11:10 pm **Posts:** 44

POL097.1-2008-12-08 Coregina (VS.NET 2003)
compiled on Dec 8 2008 21:50:11

uo::SendPacket() removed from scripts, replaced by .sendpacket method.
Uptime now 88 hours, server still alive.

taxman · **Joined:** Tue Apr 18, 2006 11:10 pm **Posts:** 44

for 118 hours of uptime manual restart executed.
no 'bad allocation' errors but there are 33 zombie connections already so core cannot finish normal way and make the save:

Code:

Current Threads:
288 - ThreadStatus
760 - Main
Waiting for 33 child threads to exit

coltain · **Posted:** Mon Dec 29, 2008 10:56 pm

same error:

pol.log

Code:

Client#819: Disconnecting client due to send() error (1): 10038
Client#501 (xx.xxx.xx.xx): disconnected (account xxxxxxxxxxx)

*Thread Info*
Semaphore PID: 0
Scripts Thread Checkpoint: 52
Last Script: pkg/pakiety/GumpSerwer/logoff.ecl PC: 35
Escript Instruction Cycles: 16496513622
Tasks Thread Checkpoint: 9
Active Client Thread Checkpoint: 116
Current Threads:
2884 - ThreadStatus
2964 - Main
*Thread Info*

no other disturbing things in other logs, no dmp was ganerated since POL didn`t crushed

(I only try to use .sendpacket(mobile))

coltain · **Posted:** Mon Dec 29, 2008 11:23 pm

after a couple minutes ater restarting I get to messages:

Socket::send_nowait() error:10053
Socket::send_nowait() error:10038
Socket::send_nowait() error:10053
Socket::send_nowait() error:10038

I searched google for a definition of this errors, but since I`m not a specialist in it... simply cant understand it

Can it be possible that this errors affect allocation??

Edit:
Taken from some forum:

Code:

10038 is "Socket operation on non-socket" which usually means that data was being sent through a socket that was already closed.  It looks like there was still something in the send buffer when vortec disconnected, which generated the error, but then vortec connected on a second attempt.

MuadDib · **Posted:** Tue Dec 30, 2008 9:23 am

Yeah, that error there is in relation to a ghosted connection in the core. Someone disconnected but the core had not caught up yet for some reason (high sysload, or it tried sending right as they disconnected).

Different error, but, might be related to an older Memory Leak, maybe. Once the new cores come out (097.2 and next 098) that massive memory leak should be fixed. (It involves .SendPacket() and Packet Objects not using SendPacket()).

Nando · **Joined:** Wed Sep 17, 2008 6:53 pm **Posts:** 55

Do you use the internal webserver? I suspect these zombie connections might be artifacts from the internal webserver...

Just fixed a bug where some threads wouldn't be properly reported in windows (but would still show in the "Waiting for xx threads..."). This doesn't fix the problem of threads stopping POL from exiting, but could give us information of where the problem is.

'bad allocation' errors

Who is online