Vulkan GPUParticles3D related error spam with multithreaded renderer

[briansemrau]

Godot version

4.0.dev (19571c9)

System information

W10, Vulkan, RTX2060

Issue description

When using GPUParticles3D in a scene with driver/threads/thread_model=2 (Multithreaded render mode), this error is printed repeatedly:

E 0:00:07:0555   RendererStorageRD::particles_is_inactive: This function should never be used with threaded rendering, as it stalls the renderer.
  <C++ Error>    Condition "RenderingServerGlobals::threaded" is true. Returning: false
  <C++ Source>   servers\rendering\renderer_rd\renderer_storage_rd.cpp:5697 @ RendererStorageRD::particles_is_inactive()

The only place this could be called every frame is here:

godot/servers/rendering/renderer_scene_cull.cpp

Line 2700 in 16dc607

if (RSG::storage->particles_is_inactive(idata.base_rid)) {

Steps to reproduce

Create a 3D scene with GPUParticles3D set up.
Enable multithreaded rendering mode.
Run project, see errors.

Minimal reproduction project

No response

[nonchip]

same for 2D by the way.

[RichardR01]

This is still an issue, when rendering is set to multithreaded. It still works, but I don't appreciate the thousands of errors spammed in the debugger.

E 0:00:04:0714   particles_get_emitting: This function should never be used with threaded rendering, as it stalls the renderer.
  <C++ Error>    Condition "RenderingServerGlobals::threaded" is true. Returning: false
  <C++ Source>   servers/rendering/renderer_rd/storage_rd/particles_storage.cpp:265 @ particles_get_emitting()

E 0:00:04:0913   particles_is_inactive: This function should never be used with threaded rendering, as it stalls the renderer.
  <C++ Error>    Condition "RenderingServerGlobals::threaded" is true. Returning: false
  <C++ Source>   servers/rendering/renderer_rd/storage_rd/particles_storage.cpp:1541 @ particles_is_inactive()

[infohub-gather]

Exact same behaviour as @RichardR01 , get a massive spam, don't think it was there in earlier versions if I recall.

[clayjohn]

This issue will be fixed by #76859