ROOM T doesn't report SB-VM:MEMORY-USAGE anymore
Bug #309083 reported by
Nikodemus Siivola
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Low
|
Unassigned |
Bug Description
In sbcl-0.8.12.51, and off and on leading up to it, the
SB!VM:
unhandled condition (of type SB-INT:BUG):
failed AVER: "(SAP= CURRENT END)"
Several clever people have taken a shot at this without fixing
it; this time around (before sbcl-0.8.13 release) I (WHN) just
commented out the SB!VM:MEMORY-USAGE calls until someone figures
out how to make them work reliably with the rest of the GC.
(Note: there's at least one dubious thing in room.lisp: see the
comment in VALID-OBJ)
It would be good to catalogue ROOM problems properly, in order to
have a fighting chance of solving them.
Changed in sbcl: | |
importance: | Undecided → Low |
status: | New → Confirmed |
description: | updated |
To post a comment you must log in.
The core part of ROOM, MAP-ALLOCATED- OBJECTS, was completely rewritten in late April, 2013. There have been two bugfixes since then, the most recent in mid-March 2014. At this point, I would suggest that it is sufficiently stable to re-enable the old ROOM-MAXIMAL-INFO logic.