OreDict Filter Freezing Gaming
Correlander opened this issue ยท 3 comments
GregTech CEu Version
v2.5.0
Modpack Used
Nomifactory CEU
Addons Installed
No response
Environment
Forge Server, but I can reproduce in singleplayer.
New Worlds
Yes
Cross-Mod Interaction
Unsure
Expected Behavior
Normally when the text hits the edge of the window it makes a new line and you are able to scroll down etc.
Actual Behavior
Instead of a line break, it just keeps going off the edge of my screen. Eventually, it won't let you type anymore after going off the screen for a bit, but it won't freeze. It only freezes if you use operators. The only one I tested with while reproducing in singleplayer was !, which successfully froze my game. Can't say 100% for the others.
Steps to Reproduce
Type in the spot where you type for an oredict filter. Continue typing. If it goes out of the window something is already wrong, but even further typing a ! will make things more wrong with a game freeze.
Additional Information
No response
Logs and more information here: https://github.com/tracer4b/nomi-ceu/issues/198
Confirmed on latest master 1fae384 . Unfortunately there is nothing useful in logs.
Problem occurs even if text is not written on "outside" of the box. I was able to replicate it on:
dustTiny*
- save successful
dustTiny* & !dust*SiliconeDioxide
- freeze
But only once, after game restart it is working without problem.
When game is in frozen state, it is just trying to match the regex which is called from:
I got to point where my stack was 300+ calls deep all in regex matcher.
Given my observations this problem is related to checking if last typed char is valid. This is done on every keystroke. And it is taking longer and longer with each character. Then it gets to point when it starts freezing game.
Confirmed on latest master 1fae384 . Unfortunately there is nothing useful in logs.
Problem occurs even if text is not written on "outside" of the box. I was able to replicate it on:
dustTiny*
- save successfuldustTiny* & !dust*SiliconeDioxide
- freeze But only once, after game restart it is working without problem.When game is in frozen state, it is just trying to match the regex which is called from:
I got to point where my stack was 300+ calls deep all in regex matcher.
Given my observations this problem is related to checking if last typed char is valid. This is done on every keystroke. And it is taking longer and longer with each character. Then it gets to point when it starts freezing game.
I had a different experience, when it froze it didn't type the character I had hit. After restart it was like that character was never typed, though I'm not sure if that's important to the issue.