Search Issue Tracker
Active
Votes
6
Found in
2018.3.0b12
2022.2.0a13
Issue ID
1107793
Regression
No
Internal error: NavMeshQuery has already been cleaned up but not deregistered from the NavMesh
Reproduction steps:
1. Open "580179 - 2018_12_06_KM.zip" project
2. Open "Entry" scene
3. Find "Kingmaker" GO in the Hierarchy window
4. "Static Config" -> "Config Document Id" -> "17360287-3a6c-4480-ae27-cb115ecf6879"
5. Enter Play Mode
6. Click "Next" until the game map is loaded
7. Look at the Console Window
Expected Result: No Errors appear
Actual Result: "Internal error: NavMeshQuery has already been cleaned up but not deregistered from the NavMesh"
Reproduced with: 2019.1.0a13, 2018.3.1f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
- Overlay Canvas are rendered on each split-screen camera when HDR is enabled
- [Android] The Player loses focus when using UnityEngine.Handheld.StartActivityIndicator() with Facebook SDK
- Build fails with "Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/gahcy/hj9mx3z/951.0 failed with output:..." errors when Scripting Backend is set to IL2CPP
CRG-Hans
Oct 18, 2022 07:06
2021.3.10f1, same issue as Nyarlathothep.
Just doing this in a FixedUpdate causes a log spam to occur:
using (var query = new NavMeshQuery(NavMeshWorld.GetDefaultWorld(), Allocator.Temp))
{
}
Using or not using the query doesnt matter.
Nyarlathothep
Mar 26, 2020 16:38
Following on from my earlier comment, it looks like using TempJob instead of Temp fixes the issue.
Nyarlathothep
Mar 26, 2020 16:23
I'm seeing this a lot in 2019.2 - it seems to be caused by using short lived queries.
In an ECS system that create/destroys a NavMeshQuery when the system is created/destroyed (i.e. long lived) I don't see the errors. On the other hand if I do something like:
using (var query = new NavMeshQuery(nav, Allocator.Temp, 512))
{
// Some work
} // <--- error here
I get an error on the closing brace, i.e. when the query is disposed.
The errors will keep spamming the console until the entire editor is restarted.
Whipexx_DigitalSun
Dec 24, 2019 11:30
Same error happening on 2019.3.0f1. Can't tell if it's the same issue as there is not enough info in the above report.