Open Wad67 opened 7 months ago
This is hard to do anything with, because you haven't provided any actionable reproduction steps, and a MRP is anything but nonapplicable.
The profiler received a crucial bugfix in 4.3, could you test if this bug still exists in that the latest dev version?
A convoluted procedural level generator is pretty much the opposite of a MRP, so I can't include that, no.
I will try the latest development version and report back, thanks.
I'm able to reproduce this issue with a build from master
at 06d51891678e3abf360d6fcd2e8bd1ba96704fcc
The platformer demo suffices.
The steps to reproduce are:
Edit: I'm not sure if the way I'm reproducing it reflects the same issue described originally by @Wad67, but the profiler hangs either way.
This is more or less it, yes. I thought it was due to the size of the project, but evidently not.
Tested versions
V4.2.1 stable b09f793f5
System information
Godot v4.2.1.stable - Ubuntu 23.04 23.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 6GB (nvidia; 535.146.02) - AMD Ryzen 5 2600X Six-Core Processor (12 Threads)
Issue description
When profiling particularly slow code, the profiler hangs, the graph shrinks as to indicate a huge peak but fails to show said huge peak.
The game instance continues to run albeit at very reduced frame-rate, inputs are not handled. Including window buttons.
I would expect that profiling would work normally, a gigantic 6000ms or so peak appearing and game execution continuing as normal.
Steps to reproduce
Have a large project with a large convoluted procedural level generator written in GDscript. Attempt to profile it
Minimal reproduction project (MRP)
N/A