Hi Naga,
Honestly your 2nd picture is blur I could not see the log clearly, but last time I meet Java Heap Space error is cause by I have pulled too much text data trying to convert them into objects to be processed and committed.
You can try monitor your device memory in task manager, see if what is happening. I suspect there is microflow or any after startup microflow is having too much data processing in once when your application startup after multiple runs.
If your problem is the data being in transaction is too much until reach your device limit, you can try to limit the microflow call handle chunk of data 1000-5000 per loop, so the microflow does not over your device's memory limit.
The Java Heap Space error you're experiencing actually indicates that your application is exhausted with the allocated memory in the Java heap. I would say, since you're using Mendix 10.11.0, which runs on the JVM, this error is tied to how Java manages memory and garbage collection.
It seems like you have already tried increasing the heap to 1024MB, which is a good starting point. But anyway, depending on the volume of data being loaded or retained in memory, this may still not be sufficient.
I have a few suggestions from my end,
As you mentioned you are facing this issue often, you can try to familiarize yourself with how Java memory management and garbage collection work. refer to this blog
You could also capture the heap dump, if its local you could do a heap dump. If it is cloud you can contact Mendix support to create a heapdump for you.