search

fenix01 / cheatengine-library

Cheat Engine Library is based on CheatEngine a debugger and coding environment particularly aimed at games, but can also be used for other purposes like debugging applications and used in schools for teaching how computers work
259 stars 79 forks source link

unloadEngine crashes #7

Open A-VORONKIN opened 8 years ago

A-VORONKIN commented 8 years ago

Hello, when I`m using unloadEngine I almost always have crashes of my app.

A-VORONKIN commented 8 years ago

Even when I'm using Example Assembler and press Unload Library this program just freeze. I'm using x64 lib. But I do this because it don't want even load library (comment everything except lib64) `/#if _WIN64/ libInst = LoadLibraryW("ce-lib64.dll"); /*#else libInst = LoadLibrary("ce-lib32.dll");

endif`*/

fenix01 commented 8 years ago

Hi ! I have successfully reproduced your bug. I don't know exactly how to solve the problem but it seems to be a problem between c# (managed code) and the library (unmanaged code).

It raised this exception 'LoaderLock'. I'm not really familiar with c# but be sure I will try to fix this error

A-VORONKIN commented 8 years ago

Thanks. I also have another error. Sometimes when I'm using iProcessAddress it returns "???" and when I'm using iOpenProcess after that I had AccessViolationException. But when I restart my app iOpenProcess and iProcessAddress works fine with same PID. Thats why I wanted to use unloadEngine. Do you know how to fix AccessViolationException? Maybe if you fix unloadEngine, iOpenProcess also will be fixed and it sometimes didn`t works because of same problem in your lib.

fenix01 commented 8 years ago

Hi Voronkin,

Sorry for this late answer, I'm very busy since a few weeks with my studies. I don't know if this bug is correlated with unloadEngine, so I will open a new ticket for the bug with IOpenProcess.

Anyway, I'm working on a new release of the library which may fix all these bugs, and add a support to python. So I'll come back to you as soon as possible.