We need to hear from more Windows 10 users. There should be quite a few in this forum. The source code looks pretty innocuous and it’s difficult to believe it causes a ‘crash’ or even a ‘freeze’. It will be interesting to see what happens on other Win10 systems.
To me a ‘crash’ is when the window disappears and you have nothing to work with. In your case it looks to me more like a ‘freeze’ or a ‘hang’. Processing’s runtime appears to have stopped processing instructions. A ‘stack trace’ with a debugger should show what caused it to ‘hang’ but unfortunately I have no idea how that could be done with a regular Processing app.