1.7.9p2 panic on lambdamoo

• Date: Sat, 16 Dec 1995 09:00:08 PST
• From:
  Judy Anderson <yduj@cs.stanford.edu>
• Posted-Date: Sat, 16 Dec 1995 09:00:08 -0800 (PST)

And the damn thing didn't succeed in writing the panic checkpoint,
either.  It got 204mb of it out!  Hardly seems fair.  But it was in
the middle of writing out the verbs; hadn't even gotten to forked
tasks.  And the core file was truncated, naturally.  We know that it
had used up somewhat more than half the available swap space, as a bit
earlier in that file we have:

Dec 16 03:00:02: CHECKPOINTING on lambda.db.new.#5# ...
Dec 16 03:00:02: *** Forking checkpointer: Resource temporarily unavailable

So either something actually managed to chew up all the available swap
space, or there's trouble in the allocator...  Unfortunately I don't
know which, and I had to blow away the truncated core file in order to
restart---we were out of diskspace.  (Probably I should have
compressed it.  Sorry, I didn't think of that until afterwards.)

24:36 lost.  Sigh.

Dec 16 03:36:13: *** PANIC: memory allocation (size 10240) failed!
Dec 16 03:36:13: #3669:has_callable_verb, line 7:  server panic
Dec 16 03:36:15: ... called from #3133:my_huh (this == #103615), line
20
Dec 16 03:36:15: ... called from built-in function pass()
Dec 16 03:36:15: ... called from #7069:my_huh (this == #103615), line
2
Dec 16 03:36:15: ... called from built-in function pass()
Dec 16 03:36:15: ... called from #26026:my_huh (this == #103615), line
2
Dec 16 03:36:15: ... called from built-in function pass()
Dec 16 03:36:15: ... called from #52563:my_huh (this == #103615), line
5
Dec 16 03:36:15: ... called from #219:do_huh, line 7
Dec 16 03:36:15: ... called from #1:huh (this == #59991), line 2
Dec 16 03:36:15: (End of traceback)
Dec 16 03:36:20: PANIC-DUMPING on lambda.db.new.PANIC ...
Dec 16 05:21:15: *** PANIC: memory allocation (size 20480) failed!
Dec 16 05:21:15: *** RECURSIVE PANIC: aborting

• Prev: 1.7.8p4 panic
• Next: 1.7.9p2 tasks
• Index: MOO-cows
• Thread: MOO-cows