It's supposed to print the biggest natural number ever (at least it attempts to). The bug is not in the code itself, though. It's in the warnings. There is a warning about 60 seconds having passed, while it's not true AFAIK.
@Dennis (pinged because of delay) What I think is that the bug resides much deeper than that, though. I don't think the interpreter is killed when output surpasses 128K, and you have said in the past that it does get killed. So, the bug is not as minor as it seems at first glance.
@EriktheOutgolfer The interpreter was previously allowed to generate a little more output than 128 KiB, to give it a chance to exit cleanly even if not all generated output would be sent to the frontend. The problem with that was that printing is very slow in Jelly, and generating 512 KiB of output took longer than a minute. Since the process was eventually killed because of the time limit, both warnings were displayed. I realize now that this is way too confusing, so I've set a strict 128 KiB limit.
Oh, so 512 KiB was the real output and 128 KiB was the visible output. I knew it was something deeper! I don't see anything bad with instantly killing the pricess, provided that, if File IO is supported by a language, it will be restricted by the sandbox, so no big damage anyways. @Dennis Seems to work now.
File I/O is by far more lenient; you can create files with sizes up to 4 MiB. What I'm worried about are huge outputs that will freeze or even crash the browser if you try writing them to a textarea.
At least on my phone, 256 KiB (the limit I had originally) is already too much.
Yeah, it somehow made my browser freeze (2013 64-bit laptop with the latest version of Chrome, Ubuntu 16.04). Also, I think that tryitonline.net should redirect to tio.run/nexus...
talk.tryitonline.net
talk.tryitonline.net