We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
App::current_user
User
When calling App::current_user from a listener callback registered on a User the thread deadlocks while waiting for the m_user_mutex to release:
m_user_mutex
realm-core/src/realm/object-store/sync/sync_manager.cpp
Lines 390 to 392 in e593a5f
But this was already taken by the calling code, here:
Lines 339 to 342 in e593a5f
This might be related to 64bf842 which was merged 3 months ago and introduced the call to user->log_in:
user->log_in
Line 361 in e593a5f
This shows a minimal reproduction in the Realm JS integration tests:
https://github.com/realm/realm-js/blob/f06739da3bcc77dce8e338b1f8960644a33be2c8/integration-tests/tests/src/tests/sync/user-listener-lockup.ts#L31-L43
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
When calling
App::current_user
from a listener callback registered on aUser
the thread deadlocks while waiting for them_user_mutex
to release:realm-core/src/realm/object-store/sync/sync_manager.cpp
Lines 390 to 392 in e593a5f
But this was already taken by the calling code, here:
realm-core/src/realm/object-store/sync/sync_manager.cpp
Lines 339 to 342 in e593a5f
This might be related to 64bf842 which was merged 3 months ago and introduced the call to
user->log_in
:realm-core/src/realm/object-store/sync/sync_manager.cpp
Line 361 in e593a5f
This shows a minimal reproduction in the Realm JS integration tests:
https://github.com/realm/realm-js/blob/f06739da3bcc77dce8e338b1f8960644a33be2c8/integration-tests/tests/src/tests/sync/user-listener-lockup.ts#L31-L43
The text was updated successfully, but these errors were encountered: