madshi.net

Hello, madshi.


My explanation is incomprehensible. I'm sorry.

Your opinion is reasonable.
I make the short sample a problem generates.
That's handed to you as soon as possible.

Please wait for several days.

Thank you very much.

Hello, madshi. I'm estimating about "2.8.2.6 beta" an offer matches. It's being tested from Windows10-32bit at present. It's a newsletter, but the movement is strange. A test, a second, a IPC queue, I become extinct and am repeating re-generation. The DestroyIpcQueue function looks normal....

Thank you very much, madshi! Right away, I'll try a beta module and confirm the problem of the DestroyIpcQueue function. Please wait for one day. It's examined whether a problem doesn't occur. A API sample of a problem is also sent to the tapir report desk of Microsoft. I'd like to be thankful for i...

Hello, madshi. A test is being also continued now. 40000 times are exceeded already. The DestroyIpcQueue function was called, but it's just normal. Your idea can't be understood, and I think it was bad. I'm sorry. It's the proposition that the size of the IPC message is restricted to 240 bytes, but ...

Hello, madshi. I thought it was significant for you to question. You pointed out, "When IPC communication isn't done at all.", a movement test of the DestroyIpcQueue function was performed. The result is interesting. Even if closure of a IPC queue and re-generation are performed 20,000 tim...

About the problem that the DestroyIpcQueue function doesn't return processing any more. I'm not testing the case to which a IPC message isn't sent. This is because it's test case which isn't needed for me. With not doing the SendIpcMessage function at all from the InjectDLL side, I can do the test w...

Hello, madshi. Thank you very much for your answer. It was understood because there was change in nativeAPIs on the WindowsOS side. Presentation is the plan to avoid which was here, but let me question with that, please. I duplicated a IPC queue on May 19 and made the experiment which opens a IPC qu...

Hello, madshi.

Two weeks have passed since I inquired.
When is release of a modified version?

I inquired to a support mail about it, but there are no answers. I think anxiously.

Please tell me an operational perspective.

Thank you.

Thank you, madshi.

I told your prospect to my customer.

I feel bad that I stopped your hand on account of me.
I expect your good work.

Thank you.

Hello, madshi. I'd like to know the schedule of corrections to explain to my customers. I used to answer "soon" before, but I want to know the specific announcement timing of the modified module. My customers also understand the circumstances and think that it is best to wait for the corre...

I carried out the idea I said before. The result was not very good. Execution of DestroyIpcQueue certainly releases the IPC queue together with memory leaks. However, if you execute it several times, it will not return from DestroyIpcQueue. I do not know the timing when this phenomenon occurs. (It o...

I am sorry to hurry. We know that the Madshi team is dealing with many difficult problems. Of course it is OK as far as possible, please make a good product. Well, I thought that I could manage this problem at present. Fortunately, fortunately DestroyIpcQueue () seems to release the IPC queue togeth...

Hello. Sorry, what happened to this memory leak issue? We imagine that madshi is busy dealing with other problems. But I'm glad if you also look at this issue. The problem of this time is 4 kbyte memory leak for IPC communication once. Our project is injected into all programs of the login session a...

Thank you for your reply. Whether the same thing happens with win10-64bit, it is thought that it will happen. In order to make HookProcessTermination of the sample project work with 64 bit, the EV signature is required for the driver, but we can not sign it now due to our convenience. Instead, when ...

I confirmed this phenomenon using "HookProcessTermination" of the sample project. We built the sample HookProcessTermination with VisualStudioExpress2012 as it is. The reproduction method is as follows. 1. Run HookProcessTermination with the latest Windos 10-32 bit. 2. Monitor HookProcessT...