The Page Unresponsive freeze happens both in the puzzle and the puzzle maker, both in Chrome and Microsoft Edge. Changing the puzzle maker structure doesn’t stop the error. Experimented and found the 2nd sequence. Changing the sequence length or engine removes the error. (edit: Added 3 more sequences.)
That’s really interesting. I wouldn’t expect a neural network to freeze or not freeze depending on the input (aside from possibly an out-of-memory error if the LENGTH of the input is too long), internally it’s just a series of multiplications and thresholds basically. It can return a wrong and/or very low confidence result but input-dependent crashing and/or freezing is hard to rationalize. Maybe someone with direct access to the code that runs the model can determine if the crash happens inside RibonanzaNet itself or in the conversion of the output to dot-bracket.
Thanks for the report. The issue is essentially a typo causing an infinite loop when resolving conflicts between multiple candidate basepairs in the game’s implementation of the hungarian algorithm. I have a fix which I aim to release soon - hopefully next week