Replies: 3 comments 3 replies
-
Really need a trace that includes the error. It will probably be huge but trace files compress well. |
Beta Was this translation helpful? Give feedback.
-
Well, there isn't any sign of an object leak or the out of memory message in the trace so there isn't enough information to debug it. I'd probably have to test the program directly. |
Beta Was this translation helpful? Give feedback.
-
Also, the version you are using is over a year old. Try the latest from https://ci.appveyor.com/project/otya128/winevdm/builds/48555490/job/kb1aaepw9aj8me0s/artifacts . |
Beta Was this translation helpful? Give feedback.
-
I am running a 16bit application on a 64 bit Windows 10 laptop using OTVDM. This is an application for reading air conditioning units. I can use all functions of the application. In the application there is an option to run a live graph. However, after about 5 minutes I get an error in the application that there is not enough memory. In the Windows log I see an error message from the GDIObject leak. How can I solve this? Anyone have experience with this?
I created a trace file.
trace_no_dll.txt
Beta Was this translation helpful? Give feedback.
All reactions