How to trace a memory leak

We have an application which will sometimes run out of memory, crash, and then recover. Is there a way to tell what is overwhelming the server and causing it to run out of memory by changing any particular log value levels or any other pointers for best practices on how to investigate a memory leak? All the documentation I find says that objects are held in memory on the client side, but there must be something preventing garbage collection on the server for it to fill up. Any ideas gratefully accepted.
1 answers

Create a support ticket and ask support to provide you with a memory dump. Do note that you need quite some knowledge and other tooling to trace these kind of problems. May be Mendix Expert Services could help you here but you would have to check that with your customer manager.