Never heard this problem before.  How about working around it by automatically closing the app if idle for more than 30 minutes?  This is good thing to do from security perspective anyway.

I cannot read the DMP files, but the following possibilities come to mind:

1. You're running out of memory or space.
    Something is still active in the program, perhaps in a loop, and it's using memory. Perhaps an object is being created that's not being destroyed at the end of the loop. Something like that is what I'd look for in the code.

2. An invalid pointer exists.
   Somewhere in the code that's running, there's a pointer to an object. Meanwhile, that object has been destroyed. The code then wants to access the destroyed object and your abend occurs.


   Check for that kind of behavior in the app. If you CAN, add some LOGGING statements into the app to try to trace what's actually going on when the app abends.


Good Luck,

Olan

Is the app doing something when this happens?  I wonder if you're running into the non-responsive window "feature" of Windows.  John wrote up an article about it here:

https://community.appeon.com/index.php/codeexchange/powerbuilder/283-not-responding-unresponsive-window-detection-prevention

Hello Bruce,

 that seems to have been the case. The memory consumption was significantly lower at this point.

Regards   Rudi