Re: Large bopm processes

Jan Chrillesen <[email protected]>
Newsgroups gmane.network.irc.bopm
Message-ID <[email protected]>
On Tue, 25 Nov 2003, Jan Chrillesen <[email protected]> wrote:

> After adding quite a few protocol lines to our bopm config the bopm
> processes have grown rather big:
> 
> bopm    73872  0.4 31.5 164016 163856  ??  S     5:30AM   3:05.71
> bin/bopm -c irc.avalonworks.ca
> bopm    74633  0.4 32.1 167444 167292  ??  S     6:20AM   2:22.50
> bin/bopm -c irc.inet.tele.dk
> 
> This is with 251 protocol lines in the config and only happens on our 2
> most active scanners. We have 2 less active scanners on the same box,
> same config, and they're only a few MB.

One of the processes grew to 500+ MB and crashed

#0  0x280ad5f8 in kill () from /usr/lib/libc.so.4
(gdb) bt
#0  0x280ad5f8 in kill () from /usr/lib/libc.so.4
#1  0x280e964a in abort () from /usr/lib/libc.so.4
#2  0x280c6383 in __assert () from /usr/lib/libc.so.4
#3  0x8050d39 in libopm_MyMalloc (bytes=152) at malloc.c:49
#4  0x80502b3 in libopm_connection_create () at libopm.c:758
#5  0x80501a1 in libopm_scan_create (scanner=0x8059140, remote=0x28010960)
    at libopm.c:679
#6  0x804ffd6 in opm_scan (scanner=0x8059140, remote=0x28010960)
    at libopm.c:514
#7  0x804df91 in scan_connect (user=0xbfbffc14, 
    msg=0x80576a0 ":irc.inet.tele.dk NOTICE TeleOPM :*** Notice -- Client connec
ting: Sz3L78 ([email protected]) [217.xx.xx.xx] {2} [Sz3L]")
    at scan.c:368
#8  0x804c6fb in m_notice (parv=0x8057640, parc=4, 
    msg=0x80576a0 ":irc.inet.tele.dk NOTICE TeleOPM :*** Notice -- Client connec
ting: Sz3L78 ([email protected]) [217.xx.xx.xx] {2} [Sz3L]", 
source_p=0x0) at irc.c:1054
#9  0x804c106 in irc_parse () at irc.c:628
#10 0x804bf87 in irc_read () at irc.c:520
#11 0x804b979 in irc_cycle () at irc.c:184
#12 0x804cc2d in main (argc=3, argv=0xbfbffd78) at main.c:195
#13 0x8049419 in _start ()
(gdb)

(IP address/hostname changed for privacy reasons)

Regards
Jan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.