Skip to content
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

OOM in MXSyncResponseFileStore #3957

Closed
manuroe opened this issue Jan 20, 2021 · 1 comment · Fixed by matrix-org/matrix-ios-sdk#1057
Closed

OOM in MXSyncResponseFileStore #3957

manuroe opened this issue Jan 20, 2021 · 1 comment · Fixed by matrix-org/matrix-ios-sdk#1057
Assignees
Labels
A-Notifications os:iOS13 T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@manuroe
Copy link
Member

manuroe commented Jan 20, 2021

Sometimes, all notifications can be displayed with "Message". Starting the app fixes the issue.

It looks like the NSE process is interrupted while managing the sync store. Dave had the issue several times.

@manuroe manuroe added T-Defect Something isn't working: bugs, crashes, hangs and other reported problems A-Notifications os:iOS13 labels Jan 20, 2021
@manuroe manuroe added this to the Sprint - Element 1.1.6 milestone Jan 20, 2021
@manuroe manuroe changed the title Corrupted sync cache in Notification Service Extension Deadlock in MXSyncResponseFileStore Jan 20, 2021
@manuroe manuroe self-assigned this Jan 20, 2021
@manuroe
Copy link
Member Author

manuroe commented Jan 28, 2021

One reason is an out of memory crash because the bg sync store becomes too big. This failure mode explains why pushes work again after opening the app: the app clears then this bg sync store.

I was able to reproduce it with a bg store of 1.5MB. I got an exception that looks like Dave's logs:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Notifications os:iOS13 T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant