Re: [bug] Memory Leak

2003-06-20 Thread Stipe Tolj 
Hi Alex,

Alex Judd schrieb:
> 
> After 300,000+ http calls in a row
> 
> access.log
> 2003-06-20 13:07:08 Log ends
> 
> enpocket.log
> 2003-06-20 13:07:07 [8] PANIC: Memory re-allocation failed
> 2003-06-20 13:07:07 [8] PANIC: System error 11: Resource temporarily
> unavailable
> 
> smsbox.log
> 2003-06-20 13:07:08 [5] ERROR: Error writing 287 octets to fd 25:
> 2003-06-20 13:07:08 [5] ERROR: System error 32: Broken pipe
> 2003-06-20 13:07:08 [5] ERROR: Couldn't write Msg to bearerbox.
> 2003-06-20 13:07:08 [0] ERROR: Error writing 287 octets to fd 25:
> 2003-06-20 13:07:08 [0] ERROR: System error 32: Broken pipe
> 
> 256M real memory on the machine so can't see that being a problem.
> 
> Ideas?

HTTP calls to what? sendsms, bearerbox's admin?

You can use valgrind (see google) to determine the leaking possition.

Stipe

[EMAIL PROTECTED]
---
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Re: [bug] Memory Leak

2003-06-20 Thread Alex Judd 
> HTTP calls to what? sendsms, bearerbox's admin?

/cgi-bin/sendsms

> You can use valgrind (see google) to determine the leaking possition.

Will do.

Alex

Re: [bug] Memory Leak

2003-06-20 Thread Alex Judd 

> You can use valgrind (see google) to determine the leaking possition.
> 
> Stipe


That'll be something like Purify on Solaris then? :)

A