@Dennis Could I bother you to (not on the live site, of course) enable core dumping and reproduce the problem? APL will dump a core file in the current directory. Zip the core and upload it at my.dyalog.com/#Account, then drop support an email including your my.dyalog user name.
I have looked at some documentation for stdbuf. This appears to be a mechanism by which the stdio functions are hijacked. That is OK provided they preserve our following uses:
1. We test whether stderr and stdout are talking to the same device. If so we ensure that we only fwrite() to one of them. So that buffering does not desturb the logical flow of the output. Testing for this is interesting when the streams may be connected to the same file via different mount points. We do our best. However, we do rely on doing a stat() on the file descriptor associated with the stream.
@Potato44 In incomplete transmission could cause the frontend to interpret the output or debugging information as errors. That won't happen anymore once I change the API to use JSON.
That link would be just short enough to fit into a post by itself. just short of 60k bytes. Good thing stack snippets let us scrape the webpage so we can generate the link using other answers.