-
-
Notifications
You must be signed in to change notification settings - Fork 24.9k
At startup ERROR: editor/progress_dialog.cpp:169 - Do not use progress dialog (task) while flushing the message queue or using call_deferred()! #100900
Copy link
Copy link
Closed
Labels
Milestone
Description
Tested versions
- Happens in v4.4.dev7.mono.official [46c8f8c]
System information
Godot v4.4.dev7.mono - Windows 10 (build 19045) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 6GB (NVIDIA; 32.0.15.6094) - Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 threads)
Issue description
I get this error sometimes at startup. My project is mostly GDScript code with two C# scripts.
This might be related to #96550, at least the error message is the same.
Godot Engine v4.4.dev7.mono.official (c) 2007-present Juan Linietsky, Ariel Manzur & Godot Contributors.
--- Debug adapter server started on port 6006 ---
--- GDScript language server started on port 6005 ---
ERROR: editor/progress_dialog.cpp:169 - Do not use progress dialog (task) while flushing the message queue or using call_deferred()!
ERROR: editor/progress_dialog.cpp:203 - Condition "!tasks.has(p_task)" is true. Returning: canceled
ERROR: editor/progress_dialog.cpp:203 - Condition "!tasks.has(p_task)" is true. Returning: canceled
ERROR: editor/progress_dialog.cpp:203 - Condition "!tasks.has(p_task)" is true. Returning: canceled
ERROR: editor/progress_dialog.cpp:203 - Condition "!tasks.has(p_task)" is true. Returning: canceled
ERROR: editor/progress_dialog.cpp:203 - Condition "!tasks.has(p_task)" is true. Returning: canceled
ERROR: editor/progress_dialog.cpp:203 - Condition "!tasks.has(p_task)" is true. Returning: canceled
ERROR: editor/progress_dialog.cpp:226 - Condition "!tasks.has(p_task)" is true.
[LSP] Connection Taken
Steps to reproduce
Unfortunately I have no idea. I feel that I have mostly seen this error when starting Godot first time after booting the computer. I did managed to get the error once by repeatedly starting Godot while Microsoft Defender was scanning the drive thus making everything slow. But even then I got the error only once with maybe 15 tries.
Minimal reproduction project (MRP)
N/A
Reactions are currently unavailable