[kaffe] bug report: core dump after eating cpu (gc related?)

[Kevin D. Kissell]

Sure looks and sounds like a memory leak to me...

----- Original Message ----- 
From: "jrandom" <auto97841 at hushmail.com>
To: <kaffe at kaffe.org>
Sent: Friday, November 21, 2003 10:31 AM
Subject: [kaffe] bug report: core dump after eating cpu (gc related?)


> Hi all,
> 
> After the last round of gc updates, kaffe has been acting much better
> with the app I'm writing (yay!)- it doesn't usually crash until after
> two or maybe three days (before it seemed to be on a 8-16 hour schedule).
>  The crashes are all the same - around when it reaches its memory limit
> (64M), it stops responding, eats 100% cpu for a while (sometimes up to
> an hour, sometimes only a few minutes) until it finally dumps core. 
> The stack is below.
> 
> I know there are surely other things involved, but running on xp w/ sun's
> 1.4.2 or 1.3.1, the application doesn't seem to have any memory leaks
> (both experientially and from profiling).  The app itself is a mixnet
> - lots of crypto, lots of network io, and very little disk io.
> 
> If anyone has any ideas for how I can debug this further, I'd love to
> help.
> 
> Thanks!
> 
> The kaffe fullversion:
> Engine: Just-in-time v3   Version: 1.1.x-cvs   Java Version: 1.1
> Configuration/Compilation options:
>   Compile date  : Tue Nov 11 11:42:10 PST 2003
>   Compile host  : col00846
>   Install prefix: /usr/local/kaffe
>   Thread system : unix-jthreads
>   CC            : gcc
>   CFLAGS        : -g -O2 -Wall -Wstrict-prototypes
>   LDFLAGS       :
>   ChangeLog head: 2003-11-11  Dalibor Topic <robilad at kaffe.org>
> 
> OS version:
> FreeBSD 4.8-RELEASE 
> 
> Hardware is a vm on a cluster, and I'm not exactly sure what physical
> hardware its on (though it has at least two CPUs).
> 
> #0  0x2815abac in kill () from /usr/lib/libc.so.4
> (gdb) where
> #0  0x2815abac in kill () from /usr/lib/libc.so.4
> #1  0x2819c13a in abort () from /usr/lib/libc.so.4
> #2  0x2817814f in __assert () from /usr/lib/libc.so.4
> #3  0x280bee85 in gc_heap_malloc (sz=280) at mem/gc-mem.c:393
> #4  0x28088deb in gcMalloc (gcif=0x280ffdb4, size=280, fidx=3) at mem/gc-
> incremental.c:1027
> #5  0x2809bcbb in newArrayChecked (elclass=0x810235c, count=130, info=0x83499a4)
> at object.c:150
> #6  0x2809efca in soft_newarray (type=5, size=130) at soft.c:86
> #7  0x081cf8b0 in ?? ()
> #8  0x00000005 in ?? ()
> #9  0x00000082 in ?? ()
> #10 0x09cd425c in ?? ()
> #11 0x0a5d8678 in ?? ()
> #12 0x00000040 in ?? ()
> #13 0x00000020 in ?? ()
> #14 0x00000082 in ?? ()
> #15 0x00000020 in ?? ()
> #16 0x09cd425c in ?? ()
> #17 0x09cd425c in ?? ()
> #18 0x0a5d86d8 in ?? ()
> #19 0x08349a40 in ?? ()
> #20 0x082cebb9 in ?? ()
> #21 0x08349a40 in ?? ()
> #22 0x081cf696 in ?? ()
> #23 0x0a5d8678 in ?? ()
> #24 0x00000066 in ?? ()
> #25 0x08342500 in ?? ()
> #26 0x0a5d8678 in ?? ()
> #27 0x08b3fabc in ?? ()
> #28 0x00000020 in ?? ()
> #29 0x0a5d8678 in ?? ()
> #30 0x00000066 in ?? ()
> #31 0x00000008 in ?? ()
> #32 0x0a5e53d8 in ?? ()
> #33 0x0000001e in ?? ()
> #34 0x0a5d86d8 in ?? ()
> #35 0x08349a78 in ?? ()
> #36 0x082cae9e in ?? ()
> #37 0x0a5d8678 in ?? ()
> #38 0x09cd425c in ?? ()
> #39 0x08342500 in ?? ()
> #40 0x08b3fabc in ?? ()
> #41 0x0a5d8658 in ?? ()
> 
> I still have the core if anyone has any ideas for further testing.
> 
> -jrandom
> 
> 
> 
> Concerned about your privacy? Follow this link to get
> FREE encrypted email: https://www.hushmail.com/?l=2
> 
> Free, ultra-private instant messaging with Hush Messenger
> https://www.hushmail.com/services.php?subloc=messenger&l=434
> 
> Promote security and make money with the Hushmail Affiliate Program: 
> https://www.hushmail.com/about.php?subloc=affiliate&l=427
> 
> _______________________________________________
> kaffe mailing list
> kaffe at kaffe.org
> http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
>