|
We are getting "Dynamic Memory Exhausted" error when our application attempts to open the connection to the UltraLite database on some of our Windows Mobile 5 devices. The average database size is 7 MB and each device usually has 60-70 MB of RAM free. The version on the deployed ulnet11.dll file is: 11.0.0.1612. According to case # 557818, this should have been fixed in 11.0.0.1611. I have tried limiting the Cache Size to 5M, 4M, 2M and still experience the issue. What is the 'appropriate value' for the cache size? Is there another fix for this issue? Thanks for your help. |
|
The case you mention limits the default cache size by observing memory available, but a subsequent fix was made to avoid cache allocation failure when the 32Mb application virtual address space is depleted. I suspect this is the problem you are seeing. This fix (#634532) is available in 11.0.1.2465 and later. Without this fix, you'll have to specify an even smaller cache size (512k?) or otherwise reduce the amount of memory your application uses. Opening the UltraLite connection soon after your application starts may also allow larger cache allocation. Setting the cache size to 512K, did not resolve the issue. I guess we will have to build our application using a later version of ulnet.dll to resolve it.
(16 May '11, 12:10)
Omar_N
Replies hidden
(Another advantage of using 11.0.1 is that it's an actively supported branch.)
(16 May '11, 15:36)
Tim McClements
1
When you upgrade to 11.0.1, you'll also have to upgrade your MobiLink server; an 11.0.1 remote can't connect to an older, 11.0.0 server.
(16 May '11, 17:23)
Bill Somers
|
