gzdoom-x64-g4.4pre-124-gb4424b2d4 crush report

[DOOMGABR [RU]]

When I'm trying to test my modification for UDMF, the test version of GZDoom crashes. The latest stable version of g4.3.3 works fine. I can’t send the mod, it is private and has bulky resources.
Link to crash report: https://drive.google.com/open?id=1wGGAW ... v69e5J8MzG

[Graf Zahl]

I can’t send the mod, it is private and has bulky resources.

Then we cannot do anything. Sorry. The crash occurs in some external DLL.

[_mental_]

It crashes inside guard64.dll which seems to be a part COMODO Internet Security. The last GZDoom frame is in I_CheckNativeMouse() function. Due to tail call optimization, the culprit is probably one of these SetCursor() calls.
Hard to say why this thing hooks this API function, maybe to protect against click hijacking. Anyway, we cannot do anything if it crashes in its own handler.

[DOOMGABR [RU]]

It crashes inside guard64.dll which seems to be a part COMODO Internet Security. The last GZDoom frame is in I_CheckNativeMouse() function. Due to tail call optimization, the culprit is probably one of these SetCursor() calls.
Hard to say why this thing hooks this API function, maybe to protect against click hijacking. Anyway, we cannot do anything if it crashes in its own handler.

Thank you, dude! It's truth, I have COMODO antivirus. May you say how can I fix this issue by myself?

[drfrag]

Adding the GZDoom process to comodo security exceptions? Or using another antivirus.

[DOOMGABR [RU]]

I added the gzdoom process to the antivirus exceptions and nothing has changed. Changing the antivirus due to the doom port is nonsense. I will not do it. There are still options, how can I get around this hook if the developers do not intend to fix this?

[Redneckerz]

I added the gzdoom process to the antivirus exceptions and nothing has changed. Changing the antivirus due to the doom port is nonsense. I will not do it. There are still options, how can I get around this hook if the developers do not intend to fix this?

Because its not GZDoom that causes the problem, as has been previously stated.

If you don't want to change antiviruses, that's on you, but at the same time you can't expect the developer to fix something that does not occur in his software to start with.

[Rachael]

I added the gzdoom process to the antivirus exceptions and nothing has changed. Changing the antivirus due to the doom port is nonsense. I will not do it. There are still options, how can I get around this hook if the developers do not intend to fix this?

Report it to the antivirus developer. It's up to them to fix things and keep it up to date if they want to introduce stupid incompatibilities like this - it's not GZDoom's fault. When GZDoom works on 99.99% of systems with no issues and your's is the only one odd one out with the issue, and your's happens to have that antivirus, it's something that only you can fix.

[_mental_]

With the commit in question reverted today, you can check tomorrow’s build.

[Guest]

It works with Comodo. Thanks, mental!