pol-core096-2006-05-30 (RC2)

Official Core: 096.7
Official Core: 097 2008-02-26

POL Home FAQ Search Memberlist Usergroups Register Profile Log in to check your private messages Log in

PenUltima Online Forum Index -> Bug Reports 096

Display posts from previous

pol-core096-2006-05-30 (RC2)

Author

Message

Lad

Joined: 05 Feb 2006
Posts: 23

Posted: Sat Jun 03, 2006 6:54 am Post subject: pol-core096-2006-05-30 (RC2)

Code:

Failed to create worker thread for Client#4820

No clock movement in 30 seconds. Dumping thread status.
*Thread Info*
Semaphore PID: 6302
("kill -SIGUSR2 6302" to output backtrace)
[0x8113654]
[0x8257009]
[0x82571ad]
[0x82637e4]
[0x82d502a]
Scripts Thread Checkpoint: 0
Last Script: scripts/ai/najemnik.ecl PC: 1078
Escript Instruction Cycles: -256713345
Tasks Thread Checkpoint: 1
Active Client Thread Checkpoint: 116
Current Threads:
6241 - Main
6302 - Listen
6303 - Tasks
6304 - Scripts
6305 - Decay_britannia
6306 - Decay_ilshenar
6307 - Decay_malas
6308 - Reap
6309 - DbgListn
6310 - ThreadStatus
6311 - Console
11990 - Client#3009
12124 - Client#3094
12231 - Client#3171
12504 - Client#3323
12522 - Client#3338
(...)

Author

Message

Shinigami
POL Core Developer

Joined: 30 Jan 2006
Posts: 292
Location: Germany, Bavaria

Posted: Sat Jun 03, 2006 1:07 pm Post subject:

man pthread_create says:

Code:

ERRORS
EAGAIN not enough system resources to create a process for the new thread.

EAGAIN more than PTHREAD_THREADS_MAX threads are already active.

I think I'll add something to output the res value...

Shinigami

Author

Message

Lad

Joined: 05 Feb 2006
Posts: 23

Posted: Sat Jun 03, 2006 1:33 pm Post subject:

hmm after this info:

Code:

[scripts/misc/logoff.ecl]: xxxx/zzzz wylogowal sie. x: 5252 y: 1838 z: 0
Client#3162: Disconnecting client due to send() error (1): 9
Client#3534 (83.211.249.110): disconnected (account xxxx)
Client#3534: Exception in i/o thread! (checkpoint=8, what=St9bad_alloc)
Client#2294: Exception in message handler 0x12: St9bad_alloc
0000: 12 00 09 24 34 36 20 30 00 ...$46 0 ........
Client#2294: Exception in i/o thread: St9bad_alloc! (checkpoint=4)
Client#2294 (83.230.229.200): disconnected (account wader)
Client#2294: Exception in i/o thread! (checkpoint=8, what=St9bad_alloc)
Client#2294: Disconnecting client due to send() error (1): 9

server just shutdown without any info Smile

Author

Message

Shinigami
POL Core Developer

Joined: 30 Jan 2006
Posts: 292
Location: Germany, Bavaria

Posted: Sat Jun 03, 2006 1:42 pm Post subject:

google says:

http://gcc.gnu.org/ml/gcc-help/2004-02/msg00232.html wrote:

When new fails to allocate the memory for an object, or new[] fails to allocate the memory for an object array, a std::bad_alloc object is thrown. In GCC, the RTTI mangled name of std::bad_alloc is, I'm guessing, St9bad_alloc.

[...]What it would do is (probably) cause your application's memory heap to become corrupted, and your program to up-n-die with a bug-in-waiting. But it may not necessarily die at the delete or delete[] ... it could run for quite some time before SEGV.

hmm...

Shinigami

	PenUltima Online Forum Index -> Bug Reports 096	All times are GMT - 4 Hours
Page 1 of 1