I'm not good at English, so I have a translation software help. It's hoped to be transmitted.
I'm using madcodehook4.0.2.
When using CreateIpcQueue(), I think I met memory leak.
I find this by Win10-32bit and don't bring by Win7-32bit,Win7-64bit.
Win10-64bit is being investigated.
The latest patch is applied to respective Windows by an echelon on May 11 (Japan time).
Win10-32bits of a problem are a Pro edition and 1703 or version OS build 15063.296.
The relevant cord is as follows.
Code: Select all
//Make IPCQueue
//madchook4.0
b_que = CreateIpcQueue("Devctl_DVCSendType", (PIPC_CALLBACK_ROUTINE)&CB_Devctl_DVCSendType,0,1,4096 );
if ( !b_que ) {
DispLog("[Error]CreateIpcQueueEx Devctl_DVCSendType");
}
//madchook4.0
b_que = CreateIpcQueue("Devctl_DVCStatType", (PIPC_CALLBACK_ROUTINE)&CB_Devctl_DVCStatType,0,1,4096 );
if ( !b_que ) {
DispLog("[Error]CreateIpcQueueEx Devctl_DVCStatType");
}
//IPCQueue Callback
void WINAPI CB_Devctl_DVCSendType(
LPCSTR pIpc,
LPCVOID pMessageBuf,
DWORD dwMessageLen,
LPVOID pAnswerBuf,
DWORD dwAnswerLen,
LPVOID pContext
)
{
memcpy( pAnswerBuf,(void *)&gDVCSendType,dwAnswerLen );
return;
}
void WINAPI CB_Devctl_DVCStatType(
LPCSTR pIpc,
LPCVOID pMessageBuf,
DWORD dwMessageLen,
LPVOID pAnswerBuf,
DWORD dwAnswerLen,
LPVOID pContext
)
{
memcpy( pAnswerBuf,(void *)&gDVCStatType[0],dwAnswerLen );
return;
}
Memory leak was observed at ProcessExplorer and VMMap.
When the performance of a property of a process of a problem is confirmed in ProcessExplorer:.
Virtual Size in Virtual Memory is about the percentage of 100 K a second, and it increases.
When it's done for a while, a process is suspended.
Size 4K of [Shareable] will be made for confirmation in VMMap in quantities.
I'm moving in Win7, so however perplexed it be whether to handle.
Beta (2.8.2.2) was tried, but it wasn't improved.
If you can have advice of improvement, it's lucky.
Thank you very much.