Closed danwood closed 2 years ago
Thank you for the bug report. I haven't had a chance to dig into this yet but I didn't want to leave you over the weekend without some acknowledgement.
I see you are using v5.4.5. Are you in a position to upgrade to the v6 SDK?
Haven't tried that yet … the strange thing is that we are only seeing these issues recently and we've been on 5.4.5 since the end of April. We can investigate moving up to v6 but that's a bigger task than we were hoping to just avoid some deadlocks …
From what I can see, we're trying to access the flag's current value which should be an immediate-return operation. I can see how there would be an async operation to save to the web for statistical purposes that the flag was evaluated. But why would the main thread be waiting for this operation to complete before it could return?
gonna withdraw our report. I wasn't the one to fix it but there was something we were doing in our code that interacted poorly here so this happened.
Is this a support request? no, it's a bug report
Describe the bug We got a deadlock between the main thread waiting for the com.launchdarkly.DiagnosticCache.cacheQueue thread, and that thread waiting for the main thread.
To reproduce Not reproducible :-(
Expected behavior We should not have a deadlock :-)
Logs Main Thread: (excerpted, this is the part called from our app's code)
Thread 2xf1bc:
SDK version 5.4.5
Language version, developer tools Xcode 13.4.1
OS/platform Mac OS Monterey 12.4
Additional context Add any other context about the problem here.