[Help-smalltalk] Playing with the VM Limits, crash on many processes

[Holger Hans Peter Freyther]

Hi all,

I created the attached torture test to get a feeling of how many processes I
can create and if my planned approach would work. With about 100.000 processes
I ran into a crash inside the GC. Compiling GST without support for the
generational GC seem not to crash.

Is this test just hitting the limit of number of objects that the GC can
properly manage? I will now build with GC_DEBUG and see what we are hitting.

regards
        holger





With the generational GC:
#2  0x0013df6e in abort () at abort.c:92
#3  0x007e1615 in oldspace_sigsegv_handler (fault_address=0x10, serious=0) at
../../libgst/oop.c:942
#4  0x008331b4 in sigsegv_handler (sig=11, sc=...) at
../../../sigsegv/src/handler-unix.c:134
#5  <signal handler called>
#6  0x007e1242 in scanned_fields_in (object=<value optimized out>,
flags=<value optimized out>)
    at ../../libgst/oop.c:1940
#7  0x007e286d in _gst_copy_an_oop (oop=<value optimized out>) at
../../libgst/oop.c:2079
#8  0x007e2b58 in scan_grey_pages () at ../../libgst/oop.c:1847
#9  0x007e38fc in copy_oops () at ../../libgst/oop.c:1755
#10 _gst_scavenge () at ../../libgst/oop.c:1229
#11 0x007e3e5c in _gst_alloc_obj (size=20, p_oop=0xbf8abd6c) at
../../libgst/oop.c:772

Without the generational GC:



The backtrace

ParallelTtest.st
Description: application/vnd.sailingtracker.track