Not Monitored
Tag not monitored by Microsoft.
36,250 questions
It's a tie.
Find the memory that has not been released and release it, but this is indeed a bug of MS API.
Help, MagSetWindowSource has memory leak, thank you.
勇强 韩
136
Reputation points
I use magnification API.
When I use magsetwindowsource + magsetimagescalingcallback, there will be a memory leak every time. I confirm that my destorywindow is successful, and that I call maguninitialize, but I don't release it.
The following is the leak stack I used umdh to grab. Please help me find out if there is a solution. Thank you.
//
// Each log entry has the following syntax:
//
// + BYTES_DELTA (NEW_BYTES - OLD_BYTES) NEW_COUNT allocs BackTrace TRACEID
// + COUNT_DELTA (NEW_COUNT - OLD_COUNT) BackTrace TRACEID allocations
// ... stack trace ...
//
// where:
//
// BYTES_DELTA - increase in bytes between before and after log
// NEW_BYTES - bytes in after log
// OLD_BYTES - bytes in before log
// COUNT_DELTA - increase in allocations between before and after log
// NEW_COUNT - number of allocations in after log
// OLD_COUNT - number of allocations in before log
// TRACEID - decimal index of the stack trace in the trace database
// (can be used to search for allocation instances in the original
// UMDH logs).
//
+ 40b7800 ( 40b7800 - 0) 5 allocs BackTrace2667B888
+ 5 ( 5 - 0) BackTrace2667B888 allocations
ntdll!RtlpCallInterceptRoutine+26
ntdll!RtlpAllocateHeapInternal+50DDF
ntdll!RtlAllocateHeap+3E
Magnification!CMilMagnifier::FilterTextureD3D9+20C
Magnification!CMilMagnifier::UpdateContentSurfaces+2A9
Magnification!CMilMagnifier::ProcessGdiDesktopBits+A2
Magnification!CMilMagnifier::SetSource+72
Magnification!Magnifier_WndProc+585
USER32!_InternalCallWinProc+2B
USER32!UserCallWinProcCheckWow+33A
USER32!SendMessageWorker+829
USER32!SendMessageW+6F
InfraCore32!IfAddHook+11846
Magnification!MagSetWindowSource+62
xcast!xcast_vdict_set_uint8+32CED4
xcast!xcast_vdict_set_uint8+32C2F6
xcast!xcast_vdict_set_uint8+32CB29
xcast!xcast_vdict_set_uint8+3297AE
xcast!xcast_vdict_set_uint8+1CB2E6
xcast!xcast_vdict_set_uint8+14749A
xcast!xcast_vdict_set_uint8+4C44E5
KERNEL32!BaseThreadInitThunk+19
InfraCore32!IfAddHook+19299
ntdll!__RtlUserThreadStart+2F
ntdll!_RtlUserThreadStart+1B
{count} votes
-
Drake Wu - MSFT 991 Reputation points2021-02-25T01:47:09.177+00:00 Hi, @勇强 韩 What is your windows version? According to the document:
Note The
MagSetImageScalingCallbackfunction is deprecated in Windows 7 and later, and should not be used in new applications. There is no alternate functionality.
This function requires Windows Display Driver Model (WDDM)-capable video cards.
This function works only when Desktop Window Manager (DWM) is off. -
勇强 韩 136 Reputation points
2021-02-25T06:17:06.087+00:00 win 10，but my code is too old to rewrite it.
-
勇强 韩 136 Reputation points
2021-02-25T06:18:09.443+00:00 And the operation is very stable, only long-term use, because of memory leakage caused by the problem, is there a solution?
Sign in to comment
Accepted answer
-
勇强 韩 136 Reputation points
2021-03-03T01:51:33.503+00:00
1 additional answer
Sort by: Most helpful
-
勇强 韩 136 Reputation points
2021-02-24T07:09:42.073+00:00 up it. I'm looking forward to your reply