Skip to content
This repository has been archived by the owner on Nov 16, 2024. It is now read-only.

Error in call to FrozenWorld.Engine: "FrozenWorld_AddEdges: (failed !edgeAlreadyExists) ..." #310

Open
zprepass opened this issue Oct 28, 2022 · 1 comment

Comments

@zprepass
Copy link

Hello. I am using the World Locking Tools version 1.5.9 and I am seeing the following error every so often in our app (49 occurrences in the past 14 days):

Exception Message
Error in call to FrozenWorld.Engine: "FrozenWorld_AddEdges: (failed !edgeAlreadyExists) Duplicate edges[4].anchorId1/2 = 13/28",

Call Stack
"CallStack": Microsoft.MixedReality.WorldLocking.Core.Plugin.checkError () (at <00000000000000000000000000000000>:0)
Microsoft.MixedReality.WorldLocking.Core.Plugin.AddSpongyEdges (System.Collections.Generic.ICollection`1[T] edges) (at <00000000000000000000000000000000>:0)
Microsoft.MixedReality.WorldLocking.Core.AnchorManager.Update () (at <00000000000000000000000000000000>:0)
Microsoft.MixedReality.WorldLocking.Core.WorldLockingManager.Update () (at <00000000000000000000000000000000>:0)
Microsoft.MixedReality.WorldLocking.Core.WorldLockingManager+UpdateProxy.Update () (at <00000000000000000000000000000000>:0)

Our app's telemetry does not show any consistent usage pattern that leads up to this exception and we do not have a repro case.
This exception usually happened after our app has run for 20+ minutes but we have seen cases where it occurred 7 minutes after the app launched.

I can use some help to understand:

  • Whether this exception would be followed by any broken functionality and if so, how would it manifest itself?
  • How can we root cause the issue and prevent it from happening?
@romsahel
Copy link

romsahel commented May 25, 2023

Hello,
I have started experiencing the same problem.
One lead I have is that I recently changed the number of maximum local anchors (whereas before it was at its default value - which means unlimited) so it might be connected to that setting but I'm having a hard time reproducing it consistently to test this.
Did you ever find a fix? I would be very interested.
Thank you,

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants