Addendum: in my case, when the memory error occurred in a webserver (hunchentoot) using YASON, the triggering object is a sb-kernel:case-failure from malformed JSON.
But it does not seem to generate a memory error when running inside SLIME, only when running as a freestanding script using SBCL init arg --script. This makes it harder to reproduce than the CL-MONAD-MACROS example.
My only evidence that the two are linked is this thread (mentioning OUTPUT-UGLY-OBJECT):
https://<email address hidden>/msg00540.html
which actually reduced the error to a much simpler case:
(with-input-from-string (in "1")
(cons (read in) in))
This also gives me "Unhandled memory fault at #x7FE8."
Addendum: in my case, when the memory error occurred in a webserver (hunchentoot) using YASON, the triggering object is a sb-kernel: case-failure from malformed JSON.
But it does not seem to generate a memory error when running inside SLIME, only when running as a freestanding script using SBCL init arg --script. This makes it harder to reproduce than the CL-MONAD-MACROS example.
My only evidence that the two are linked is this thread (mentioning OUTPUT- UGLY-OBJECT) : /msg00540. html
https://<email address hidden>
which actually reduced the error to a much simpler case:
(with-input- from-string (in "1")
(cons (read in) in))
This also gives me "Unhandled memory fault at #x7FE8."