The thread in the bugboard (there is one since 1.16, refreshed for 1.18) has 2 sources or even more that show the prob, so I didn't think an additional link would be needed.
Even in this thread there is one...
So far it seems like everything is able to break it after 5-7 hours ... (depending on the systems speed even longer) Most just don't let the stuff run that long.
The thread in bugboard has simple loops with peekevent(), the one here is a simple forever loop with a delay ...
The ideas on the reason so far have mostly been focused around a "flooded event queue" problem that lets BM loop forever ... Which is somewhere reasonable as some parts of BM changed between 1.12 and 1.16 like the internal event hook to handle user input and the like. This introduction did (if I haven't missed it) not introduce an automatic data drop on events on the queue, if it has not been used any longer (say after a given amount of time), which perhaps might be needed to prevent the queue from beeing filled up and break. (don't know how Windows handles event OS side ... but if it is a buffer then it might fill up that buffer and create problems if the BM app did not remove the processed events from there)
Even in this thread there is one...
So far it seems like everything is able to break it after 5-7 hours ... (depending on the systems speed even longer) Most just don't let the stuff run that long.
The thread in bugboard has simple loops with peekevent(), the one here is a simple forever loop with a delay ...
The ideas on the reason so far have mostly been focused around a "flooded event queue" problem that lets BM loop forever ... Which is somewhere reasonable as some parts of BM changed between 1.12 and 1.16 like the internal event hook to handle user input and the like. This introduction did (if I haven't missed it) not introduce an automatic data drop on events on the queue, if it has not been used any longer (say after a given amount of time), which perhaps might be needed to prevent the queue from beeing filled up and break. (don't know how Windows handles event OS side ... but if it is a buffer then it might fill up that buffer and create problems if the BM app did not remove the processed events from there)