hi dave,
Same happens here - It looks like a racket bug. I tried freeing and
deleting it, resulting in crashes, checked the docs for
scheme_utf8_encode_to_buffer and it claims it allocates with
scheme_malloc_atomic which should use the gc.
i tried the same, and came to the same conclusion.
The next thing would be to write a small c program to replacate this and
post it to the racket list.
have you submitted a bug like this earlier? do you have a template we
could base the small program on?
best,
gabor
