Regression failures with verify_gens etc

Bug #1983864 reported by Douglas Katzman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
New
Undecided
Unassigned

Bug Description

Some continuous build should run the test suite with heap verifications.
I've recently observed three failures (all irreproducible of course).
Perhaps these are due to enabling sb-sprof in parallel-exec.
If the failure rate goes to 0 with that off, it's probably a safe bet that sprof is to blame.
(Ironically the defstruct failure is while trying to produce the sprof report, but the sprof graph creation code is extremely unlikely to be the root cause of anything)

1. defstruct.impure
BEGIN gc_gen(0,1)
/pinned objects(g0): large=1 (113800 words), small=17
Verify after GC(0) [threads] [RO] [static] [dynamic]fatal error encountered in SBCL pid 2269301 tid 2269301:
GC invariant lost, file "verify.inc", line 323

GC: stw_delay=31,50,79 µs (min,avg,max) pause=83493,187547,424341 µs (sum=5438877) over 29 GCs
   0: fp=0x7f5e64727310 pc=0x1001e0c96b SB-SPROF::%MAKE-NODE
   1: fp=0x7f5e64727378 pc=0x1001e5940c SB-SPROF::MAKE-NODE
   ...

2. compiler.impure
BEGIN gc_gen(0,1)
/pinned objects(g0): large=0 (0 words), small=21
Verify after GC(0) [threads] [RO] [static] [dynamic]Ptr 0x1004799953 @ 100491e860 (lispobj 100491e867,pg2339) sees junk
fatal error encountered in SBCL pid 1975592 tid 1975592:
Verify failed: 1 errors

3. hash-table.impure
BEGIN gc_gen(0,0)
/pinned objects(g0): large=0 (0 words), small=94
CORRUPTION WARNING in SBCL pid 2003898 tid 2003898:
Memory fault at (nil) (pc=0x561546bc6be5, fp=0x7f9cac7be1c0, sp=0x7f9cac7be180) tid 2003898
The integrity of this image is possibly compromised.
Exiting.

Revision history for this message
Douglas Katzman (dougk) wrote :

possibly unrelated random failure-

::: UNEXPECTED-FAILURE :FLUSH-VECTOR-CREATION due to SIMPLE-ERROR:
        "Expected the form
             (FUNCALL F)
         NOT to cons, yet running it for 10000 times resulted in the allocation
         of 82096 bytes (8.210 per run)."

Revision history for this message
Stas Boukarev (stassats) wrote :

The consing tests are always somewhat unreliable.

Revision history for this message
Douglas Katzman (dougk) wrote :

Bad interaction between a timer test and the compiler now? (from timer.impure)

::: Success (:TIMER :PARALLEL-UNSCHEDULE)
While evaluating the form starting at line 248, column 0
  of #P"/tmp/sbcl/tests/timer.impure.lisp":
Unhandled UNBOUND-VARIABLE: The variable SB-C::*LAST-MESSAGE-COUNT* is unbound.
Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {10044280A3}>
0: (SB-C::NOTE-MESSAGE-REPEATS #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDERR* {1000009633}> T)
1: (SB-C::%PRINT-COMPILER-MESSAGE #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDERR* {1000009633}> "caught WARNING:
~@< ~@;~A~:>" ("Timer #<TIMER \"ticker 2\" {100414C603}> failed to interrupt thread #<SB-THREAD:THREAD \"scheduler 1\" FINISHED values: NIL {100414C063}>."))
2: ((LAMBDA NIL :IN SB-C::PRINT-COMPILER-MESSAGE))
3: (SB-IMPL::CALL-WITH-SANE-IO-SYNTAX #<FUNCTION (LAMBDA NIL :IN SB-C::PRINT-COMPILER-MESSAGE) {10041CE63B}>)
4: (SB-C::COMPILER-WARNING-HANDLER #<SIMPLE-WARNING "Timer ~S failed to interrupt thread ~S." {10041CDDF3}>)
5: (SB-KERNEL::%SIGNAL #<SIMPLE-WARNING "Timer ~S failed to interrupt thread ~S." {10041CDDF3}>)
6: ((FLET SB-KERNEL::%WARN :IN "SYS:SRC;CODE;WARM-ERROR.LISP") "Timer ~S failed to interrupt thread ~S." #<SB-KERNEL::CONDITION-CLASSOID WARNING> SIMPLE-WARNING #<TIMER "ticker 2" {100414C603}> #<SB-THREAD:THREAD "scheduler 1" FINISHED values: NIL {100414C063}>)
7: ((FLET SB-IMPL::RUN-TIMERS :IN SB-IMPL::RUN-EXPIRED-TIMERS))
8: ((FLET SB-THREAD::WITH-SYSTEM-MUTEX-THUNK :IN SB-IMPL::RUN-EXPIRED-TIMERS))
9: ((FLET "WITHOUT-INTERRUPTS-BODY-5" :IN SB-THREAD::CALL-WITH-SYSTEM-MUTEX))
10: (SB-IMPL::RUN-EXPIRED-TIMERS)
11: ((FLET SB-THREAD::EXEC :IN SB-SYS:INVOKE-INTERRUPTION))
12: ((FLET "WITHOUT-INTERRUPTS-BODY-1" :IN SB-SYS:INVOKE-INTERRUPTION))
13: (SB-SYS:INVOKE-INTERRUPTION #<FUNCTION (FLET SB-UNIX::INTERRUPTION :IN SB-UNIX::%INSTALL-HANDLER) {7F1C4DBBDFAB}>)
14: ((FLET SB-UNIX::RUN-HANDLER :IN SB-UNIX::%INSTALL-HANDLER) 14 #.(SB-SYS:INT-SAP #X7F1C4DBBE370) #.(SB-SYS:INT-SAP #X7F1C4DBBE240))
15: ("foreign function: call_into_lisp_")
16: ("foreign function: funcall3")
17: ("foreign function: interrupt_handle_now")
18: ("foreign function: #x5634848B7381")
19: (SB-C::MAKE-COMPILATION) [external]
20: ((FLET "LAMBDA0" :IN "SYS:SRC;COMPILER;TARGET-MAIN.LISP"))

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.