RLMException - mmap() failed: Cannot allocate memory size: #8523
Labels
Encryption:On
Frequency:Always
More-information-needed
More information is needed to progress. The issue will close automatically in 2 weeks.
O-Community
Repro:No
SDK-Use:Local
T-Bug
Waiting-For-Reporter
Waiting for more information from the reporter before we can proceed
How frequently does the bug occur?
Always
Description
In the scenario I use, I have several queues, the main thread, the work serial queue, and some child threads. The main thread mainly listens for data changes through the realm observe and feedback on the UI, and the work serial queue is used to perform data write operations. The child thread is mainly used to read realm data while working on business scenarios. It rarely changes, and if there is a change, I will put it in the work queue. But there are errors related to # mmap() failed: Cannot allocate memory size: and bad::alloc, and I want to know how I can modify my code to reduce the occurrence of these errors.
I have a few questions:
But there are some databases that read frequently, and I will try to hold these relam handles in different threads.This was also done when we used version 10.13, but this error did not occur.
3、Is there any way to monitor how much mmap space relam is using?So I can try to do some analysis from memory.
From what we can see, it seems to be an issue after realm was upgraded from 10.13 to 10.43, but we don't know what possible cause affected this at this time. It would be better if you could help me provide some analytical ideas, thank you!
Stacktrace & log output
I can't reproduce it, it exists in our production environment version
Can you reproduce the bug?
No
Reproduction Steps
No response
Version
10.43
What Atlas Services are you using?
Local Database only
Are you using encryption?
Yes
Platform OS and version(s)
ios17.1.2
Build environment
Xcode version: 15.2
The text was updated successfully, but these errors were encountered: