It's great to hear that this was resolved! The problem was that the JVM was running out of code cache space.

I'm impressed by the previous discussion here:

https://news.ycombinator.com/item?id=33865932

It was posted to HN at 2022-12-05T14:18:56. The top comment, correctly suggesting that the problem was with the code cache, was posted at 2022-12-05T15:09:31 by ulularem; that's less than an hour from HN submission to identifying the solution. I don't know if it was the HN comments or one of the other community discussions that first highlighted the code cache to the Lichess maintainers, but I'm impressed that HN could collectively debug this frustrating issue so quickly.

Very nice! Good job to everyone especially those pointing out that this might be the problem in the previous thread.