[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#25386: guile-2.0 and 2.2 thread leakage+crash; very simple test atta
bug#25386: guile-2.0 and 2.2 thread leakage+crash; very simple test attached.
Sat, 7 Jan 2017 15:47:51 -0600
The (very simple) program below leaks ... something, very rapidly, and
then crashes after about 15-30 seconds. Last thing printed before
((gc-time-taken . 2791348254) (heap-size . 7532883968) (heap-free-size
. 2449408) (heap-total-allocated . 23912882640)
(heap-allocated-since-gc . 1073995264) (protected-objects . 90)
(gc-times . 87))
Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
Similar issue in guile-2.2 except it takes longer (8 minutes) and
crashes in gc somewhere. I assume that some sort of
continuation is left lying about, even though the thread has
(define junk 0)
(define halt #f)
(define start (- (current-time) 0.1))
; Create thread that does junk and exits. Yes, the increment
; of `junk` is not protected, and its racey, but so what.
(define (mkthr v) (call-with-new-thread (lambda () (set! junk (+ junk
; thread arguments
(define thrarg (make-list 10 0))
(define cnt 0)
; Create a limited number of threads
(define thr-list (map mkthr thrarg))
; (display (length (all-threads)))
(map join-thread thr-list)
; Some handy debug printing.
(set! cnt (+ cnt 1))
(if (eq? 0 (modulo cnt 500))
(display (/ cnt (- (current-time) start))) (newline)
(display "num threads=")
(display (length (all-threads))) (newline)
(display (gc-stats)) (newline) (newline)
; tail recursive infinite loop.
(define (aloop) (mke) (if (not halt) (aloop)))
; while forever.
; Run elsewhere, so that we have a shell prompt
; (not required for the bug)
; halt if desired.
; (set! halt #t)
- bug#25386: guile-2.0 and 2.2 thread leakage+crash; very simple test attached.,
Linas Vepstas <=
- bug#25386: Manual gc helps, Linas Vepstas, 2017/01/07
- bug#25386: test case update, Linas Vepstas, 2017/01/08
- bug#25386: calling gc too often triggers a crash, Linas Vepstas, 2017/01/08
- bug#25386: Please ignore previous stack trace., Linas Vepstas, 2017/01/08
- bug#25386: This can be closed, Linas Vepstas, 2017/01/11