This is a patched library that solves this issue:
https://drive.google.com/file/d/1LvXqn-pnH0Rf7pUKKx4vh-IJ8vXp84HD/view?usp=sharing

Could you please try it?

Will try it, thank you!

BTW is there a way how I can recognize duplicates upfront so I don't spam your bug tracker with false ones?

is there a way how I can recognize duplicates upfront so I don't spam your bug tracker with false ones?
Dumps having similar callstacks on the final call lines (dll addresses) will point to the same crash.
But don't worry, we can detect duplicates very easily once we open the crash dumps and organize the bugtracker accordingly.

Thank you! As we will release in a week on 12th of November: I have rolled back to 3.2.4 p8 on our stable (release) branch but have 3.2.5 p1 in our beta branch to monitor potential issues.

Is it kind of realistic to have the crashes kind of fixes I've reported here? I know it might be a tricky question and I know that we're probably using Noesis in kind of an unconventional way so to say with stressing it a lot with our map stuff...

Thank you again for always reacting that quickly! Much appreciated!

Is it kind of realistic to have the crashes kind of fixes I've reported here?

Yes, I've sent you a debug library to get more info on these related crashes. As soon as we get your feedback we'll try to fix them.
Thanks for all your collaboration!

Thank you! Added it to our dev branch. And thank you for all your help!