Starting a code run straight after the GUI loads can cause timing errors

If someone starts a code run (an example, or code in the buffers, etc) as soon as the GUI has loaded, the run can slow down or come to a halt with timing errors - perhaps because the audio setup is still being finalised somehow? Not 100% sure if it's a quirk of my setup or not.

Please see the attached gif for an example.

Granted that this may be a bit of an edge case, but I suspect for folks that might want init.rb to run something on startup, this would be even more of an issue. It seems to me that we'd prefer this audio setup to be complete before someone is able to run anything, in order to prevent such timing issues.