Process is frozen and use 100% CPU

[dimonb]

Preliminary checks

• I've checked that there aren't other open issues on the same topic.
• I've checked that this issue is reproducible on the latest snapshot build.

Platform

macOS

Describe the bug

Game is frozen with 100% cpu usage when casting blood last (not reprodusable

process sample in attachment
Sample of fheroes2.txt

Save file

Not reproducible, save file make no sense

Additional info

No response

[oleg-derevenetz]

Hi @dimonb did you notice if the usual animations on the battle screen were working at that time (for example, were the flags of the heroes flying)?

I got the impression that the bloodlust animation went into an endless loop because SDL_mixer reported that the bloodlust sound effect was still playing, although this was actually not the case. If so, then why exactly this was happening is hard to tell, because I also can't reproduce this effect so far.

[ihhub]

Hi @dimonb , can you please reply to the original question?

[dimonb]

Hi guys, sorry for delay. No other unusual animation. I got this one more time :( also blood last
It is the only case when game stuck with 100% CPU

[ihhub]

Hi @dimonb , if we provide a special version of the engine would you be able to compile it on your machine? We will provide instructions.

[dimonb]

hi @ihhub !
yes, sure

[ihhub]

@dimonb , I have an idea in mind how to fix or at least narrow down the problem so I will create a separate pull request from where you might check out the branch. I will do it after the upcoming release which is in a few days. If I miss creating a pull request please ping me again next week.

[ihhub]

@dimonb , actually, I made a pull request #8698 for this matter. I set 20 seconds as a hard stop for playing Blood Lust sound. Could you please compile and test it on your side? 20 seconds would be enough to identify that this was a deadlock. To test I suggest to use Battle Only mode which is designed for battles.

[dimonb]

@ihhub will try in several days, thx!

[ihhub]

Hi @dimonb , have you tried the fix?

[dimonb]

Yes, could not reproduce any more On 27 Jul 2024, at 13:21, Ihar Hubchyk ***@***.***> wrote: Hi @dimonb , have you tried the fix? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>