Since 0.10.15 Foundry gets unusable on GM client when players moves token (endless Loop condition?)

[STBaf]

I don't have the exact circumstances together yet, but since the 0.10.15 update, Foundry became unusable on the GM's computer during our DnD5 round when one of the players dragged his token around. There were quite a few more tokens/players on the scene though. (5 players + 1 GM + enemies controlled by GM. See picture).

Browser did go in a full non-responsive state for the thread that handles the webpage view, nothing inside the page was clickable (browser UI elements itself still worked normal). After a while the usual "Your page is not responding, do you want to wait or abort" message was shown by browser. Sometimes with small movements there was the non-responsive behavior, but after some seconds there was short responses while calculating distances and/or pathfinding (looks a little bit like 1 fps all 5-10 seconds then for the page).
Looks like some javascript is running in a endless loop at some point when users move their token and something is calculated by that on the GM side (FunFact: seem not to happen when the GM moves tokens by itself, only when a user move a token the GM client starts to stutter).

Aside from the 0.10.14 -> 0.10.15 update (I opened the issue with the tokens move through walls and did that one module update singular by pressing the update button on the module, not update all) nothing changed on my configuration.

Disabling Elevation Ruler in that world "fixed" the problem (better say: made it disappear because for obvious reasons).

Configuration is Foundry v12.331, DnD5e 3.3.1, Elevation Ruler 0.10.15 (now) (and a bunch of other modules for sure). We didn't had that problem with 0.10.14 as said.
Running on a datacenter hosted server by NodeJS and using Edge (Edge with Chromium engine 130.something.something actual version) without any extensions in the browser (that's mainly why I use Edge - do have a module free only for that use case browser).

[STBaf]

Additional Info: Something is seemingly very strange with the Pathfinding. Stopped working for players, but when I drag tokens I seem to see a lot of old Pathfinding ways (or better: I guess that are old Pathfindings)

[AngelofWoe]

I'm having similar issues.
When my players move tokens, the text gets larger and larger infinitely and lags out my PC or outright crashes Foundry, seemingly using a massive amount of CPU/GPU to render infinitely larger fonts.
When I move tokens after this starts happening, huge chunks of the scene go black and flicker on and off.
Text on measurement ruler sometimes does the opposite on the GM end, where it will become the minimum font size and utterly unreadable.
I've had a hard time capturing examples, but here's one with the text becoming enormous as one of my players is moving their token (it gets much, much bigger than this, going much larger than my entire screen per number):

Turning off "Scale Ruler Text" doesn't seem to help.

[TheDSeraph]

Experienced the same issue as AngelofWoe and had to revert to 0.10.14

[Nedrapter]

Same issue as the above here! Make the game unplayable when it happens.

[pandanielxd]

I think I am experiencing the same thing as AngelofWoe, but disabling scale ruler text did seem to help from the testing I've done 🤔.

Getting this error with it enabled, freezing the game.

Might be something else though?

[caewok]

I fixed an issue with how the ruler text scales in v0.10.16; that may address this issue as well.

[pandanielxd]

I fixed an issue with how the ruler text scales in v0.10.16; that may address this issue as well.

Sadly didn't change anything to how the text scales up repeatedly, got the same error.

[caewok]

Took another shot at the text scaling issue in v0.10.17. Definitely fixed some issues I saw with the text font size going to 1. Not sure about infinitely large text, which I have not seen.

[pandanielxd]

Took another shot at the text scaling issue in v0.10.17. Definitely fixed some issues I saw with the text font size going to 1. Not sure about infinitely large text, which I have not seen.

Seems to work from the testing I've done now. Cheers!