|
From: Ype K. <yk...@xs...> - 2001-03-02 19:59:06
|
Gerhard, ... >then the first problem was gone but I ran into the next >when I started the simple example program > >Maybe you can help me once more >thank you >gerhard > > >gerhard@darkstar:~/work/prog/jython > jython Demo/awt/simple.py >SIGSEGV 11* segmentation violation > stackbase=0xbffff150, stackpointer=0xbfffefc4 > >Full thread dump: > "Finalizer thread" (TID:0x40596210, sys_thread_t:0x412dae0c, >state:R) prio=1 ... It looks like the java VM crashes during garbage collection, more precisely: during finalization. The first time you run jython after installation it needs more memory because it initializes a package for each jar file it finds. Increase memory and try again: use java -help adapt the jython script. As you are using a Pentium II and the default Suse JVM the following may not apply: I had the SIGSEGV problem using the blackdown JVM's on ppc, iirc both versions 1.1.8 and 1.2.2 1.3 crashes in a more 'friendly' way: it gives up with an out of memory error. All this happens with the default 30Mb, but also with 160Mb of memory. Unfortunately the problem persists under 1.3: running a simple python program can make the JVM give up quite regularly, but in a seemingly random way, independent of the amount of memory used. I reported the problem to blackdown some time ago (for 1.2.2) but I had no reaction. Since upgrading the 1.3 helps only a bit I am considering moving to other hardware. Please note that all this is on ppc. I have not heard of similar problems on x86. Good luck, Ype P.S. You might consider using the jython-user list for similar situations. |