Editor maxes out CPU thread on beefy system, runaway thread suspected

[thelabcat]

ChroMapper version
0.10.779 Linux

Describe the Issue
While in the editor, a thread of my CPU consistently and instantly maxes out. My cooling fan kicks on high. This is a beefy system, it handles GTA5 on max settings with ease. ChroMapper shouldn't be causing this.

Steps to Reproduce

1. Platform is Fedora 40 x64
2. Open ChroMapper to the editor on any map (even an empty one).

Expected Behavior
My system to generally remain cool, definitely not kicking into high gear.

Additional Context
I do not experience lag or ChroMapper stutters when this happens. I suspect the problem is caused by an event or rendering loop that is not limited in how many times it can loop per second (this would be an "FPS limit" if it were graphics), thus it is running as fast as it can all the time needlessly.

[Caeden117]

the FPS Limit doesnt just limit GPU usage - reducing the event loop would also reduce workload on the CPU. ChroMapper has two settings related to this, the VSync and Maximum FPS setting.

If these settings don't help, try checking the Wiki section on increasing your performance. The performance increases should also reduce the workload demand on your CPU.

[thelabcat]

I turned the FPS limit down to 10, and it limited it back up to 15. So far, so good. But loading up the editor, this is the fastest 15 FPS I've ever seen: I could not tell any difference at all. It also did not affect the runaway loop. I think the FPS limiter is broken.

[thelabcat]

Strike that, I turned off monitor frame rate sync (aka VSync) and the regular frame limiter is working now. So, I don't know if VSync is supposed to supersede the frame rate limit, but it does.

[XAce1337manX]

VSync superseding fps limit is intended. Unity requires VSync off for target frame rate cap to have an effect.
Can update the tooltip to specify this behaviour.