hippoedit.exe keeping handles to external tools

[Scott Bilas]

I have lua.exe set on a hotkey to run as an external tool and use it to test and run some lua code I'm working on.

Sometimes (not always) HE keeps a handle to the process after it has completed running. I know this because when I rebuild lua.exe it doesn't work. VS gives me an error that it can't delete lua.exe because it's in use. A quick check with ffunlock.exe shows me that hippoedit.exe has three open handles to lua.exe.

Now, I'm capturing the output of lua.exe. So I'm assuming that when HE runs lua, it keeps handles open to it so it can redirect the output to itself to put in the output window.

So there's some bug with HE not releasing those handles. If I restart HE, then the handles are released and I can rebuild lua.exe. Then maybe a day later the problem starts again. As I said it's not consistent or easy to reproduce.

UPDATE: forgot to mention that this is HippoEDIT 1.42.650 on Vista x86.

[Arthur]

Interesting, even though I have not run CScript (VBScripts) today even once, I can still see a reference to it listed.

PS: Wanted to add that the Process Explorer tool does not show that being the case.

[alex]

Hi Scott,

I have reproduced it only once :/. After first time, executable I have tested was always released correctly.
But I have done some fixes there (you was right, some handles were not closed).
Let us see and check once more in new beta.

Best regards,
Alex.

[Scott Bilas]

I'm sorry to report that this is still happening. I went to rebuild lua.exe again (it's a standard part of our build process for the toolchain on our game) and it was locked by HippoEDIT. When I restarted HE then I was able to rebuild lua.exe. I confirmed with ffunlock.exe first. One handle was still open to lua.exe.

This is with 1.43.655.

[alex]

Hello Scott,

yes it is a pity. The bad thing that I can not reprodcue this. Was able only once. Then did the correction and could not reproduce.
Ok, I will check once more.

If you can reproduce it easy, would be glad for example.

Best regards,
Alex.

[Scott Bilas]

You might try stress-testing. I wasn't able to reproduce the exact problem, but I did manage to get a lot of lua.exe's hanging around and never terminating.

I got this to happen by just holding down the F5 key (this is what I have my lua.exe tool mapped to) so it repeats heavily for maybe 5 seconds. Lots of processes launched and never finished.

Is it possible that the problem I am still having with hippoedit.exe is that I'm accidentally running the tool more than once? Say the first lua.exe stalls and I hit F5 again, and the second one runs at the same time. Should the Output window serialize these requests instead of running them in parallel, when the "capture output" option is selected?

[alex]

Yes, this is good idea. I would try that. Thanks!

I think I would not implement serialization (it is not a standard behaviour for tools in other programs) but need to check, that no tool, capturing output, started already.