-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EXC_BREAKPOINT DemandBuffer.swift:111 BUG IN CLIENT OF LIBPLATFORM: Trying to recursively lock an os_unfair_lock #114
Comments
Does it happen with operators that use DemandBuffer? Or is it just CurrentValueRelay? |
@freak4pc I've managed to repro it with |
Those all use Relays I believe. Would be interesting to see if it happens with just random non-subject/relay operators. |
Hi, I've started having those kind of errors as well using a ReplaySubject. |
I unfortunately don't have the time to debug this anytime soon, but happy to review a PR if anyone wants to dig into this and find a trustworthy fix. Thanks! |
@dsk1306 sorry to awaken this thread but any change you have an example that can reproduce this somewhere ? I know it's been a while but seems like this is still happening. |
@freak4pc Sorry, we dropped iOS 13 support in our app 🤷🏻♂️ So I cannot provide any more details. |
Same issue on iOS 17.2.1
|
Is there any updates on this issue? Crash happens on iOS 17.1.1
|
I've just received a huge amount of crash reports caused by an exception during the
DemandBuffer
deallocation on iOS 13.I've tried to repro it and it looks like it just enough to create a publisher that uses
DemandBuffer
(e.g.CurrentValueRelay
), initialise it and the just deinit it. And it looks like it only reproducible on iOS 13.5 and older.Did anyone else had the same issue?
The text was updated successfully, but these errors were encountered: