Reply to thread

Message

<blockquote data-quote="Pablik" data-source="post: 1299703" data-attributes="member: 106554"><p>In your log we can see:</p><ul>
<li data-xf-list-type="ul">you are running x86 version of MediaPortal. The 32bit version has limit of memory usage regardless of physical memory size.</li>
<li data-xf-list-type="ul">your system is going to suspend/resume every hour. This causes to close the databases movingpictures.db3 and FanartHandler.db3. I believe reopening the database is causing memory fragmentation and becouse you are running 32bit version the system simply can't find not enough free memory hole.</li>
<li data-xf-list-type="ul">I made updated version of MovingPictures(based on latest version) where the database uses flushing the memory content to the disk instead of closing the DB upon suspend. You can find the new dlls in the attached file. Backup the originals and the database also(movingpictures.db3) first. Now you should see in movingpictures's log these events: Synchronous() True/ Synchronous() False. You should not see in the MediaPortal's log 'SQLiteClient: Closing database: movingpictures.db3' anymore(before going to suspend).</li>
<li data-xf-list-type="ul">I recommend to switch the MediaPortal to x64 version</li>
</ul></blockquote><p></p>

[QUOTE="Pablik, post: 1299703, member: 106554"] In your log we can see: [LIST] [*]you are running x86 version of MediaPortal. The 32bit version has limit of memory usage regardless of physical memory size. [*]your system is going to suspend/resume every hour. This causes to close the databases movingpictures.db3 and FanartHandler.db3. I believe reopening the database is causing memory fragmentation and becouse you are running 32bit version the system simply can't find not enough free memory hole. [*]I made updated version of MovingPictures(based on latest version) where the database uses flushing the memory content to the disk instead of closing the DB upon suspend. You can find the new dlls in the attached file. Backup the originals and the database also(movingpictures.db3) first. Now you should see in movingpictures's log these events: Synchronous() True/ Synchronous() False. You should not see in the MediaPortal's log 'SQLiteClient: Closing database: movingpictures.db3' anymore(before going to suspend). [*]I recommend to switch the MediaPortal to x64 version [/LIST] [/QUOTE]

Verification