[trsqr]

==1433== LEAK SUMMARY:
==1433== definitely lost: 0 bytes in 0 blocks
==1433== indirectly lost: 0 bytes in 0 blocks
==1433== possibly lost: 0 bytes in 0 blocks
==1433== still reachable: 26,208 bytes in 69 blocks
==1433== suppressed: 0 bytes in 0 blocks

:-) That would prove you wrong in deed. Retry with: --leak-check=full ?

Yes, indeed it seems that the memory is released when Kodi is quit. Though I don't know where I was wrong - I am just reporting what I see. If there are some other printouts in addition to passing the leak-check=full parameter to valgrind that I can collect while observing the growing memory usage percentage I could collect those as well. I'll retry this probably on Monday.

Of course it is possible that OE gets stuck due to some other reason and not because of memory. However, the fact that any add-on does not start anymore could point to a memory issue.

I did not notice this problem, but was talking to another guy who had the same issue (OE crashing after watching several videos) on the same hardware but 2GB RAM - I just verified that it indeed happens.