ROOM T doesn't report SB-VM:MEMORY-USAGE anymore

[Nikodemus Siivola]

  In sbcl-0.8.12.51, and off and on leading up to it, the
  SB!VM:MEMORY-USAGE operations in ROOM T caused
 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.

[Alastair Bridgewater (alastair-bridgewater)]

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.

[Alastair Bridgewater (alastair-bridgewater)]

These were restored in 5b3d3786f2eed5f3d869af31204587a2fa617ad5, which was released as part of sbcl-1.3.21.