Hi all –
Thanks for your patience on this one.
First off, @Patrick, that hunch was unfounded. Nothing to see here.
Secondly, as I’ve mentioned, we’ve seen this in a few cases now, and at first we thought it was limited to the Breakdown app, but as @tk421storm suggests, it does seem to crop up whenever there’s printing to the Python console going on.
I brought this in front of an engineer this morning, and he has a good hunch: we are using Python’s
print function to display any logging output in the Python console. In 3ds Max, we had an issue where we had to forward
print calls to the main thread, because the Python interpreter would blow up when we used a background thread. So, the suspicion is that there is a regression in Nuke 12 (and maybe 11?) that behaves the same way?
We had an internal ticket for this bug, but we’ve bumped up its priority substantially. I’ve linked this post to the internal ticket, so we’ll be notified when it’s resolved, and will notify you all in turn.
It’s indeed a challenge when the tools you use to debug the crash are what’s causing the crash in the first place. Thanks to everyone who chimed in with ideas of how to get around it! We’ll keep you posted.