FViktor

I know, that's sad.. I’m not at all familiar with the update cycle, but doesn’t wx 3.0.5 and 3.1.2 need to be released first? At least the fix is on its way, thanks to me so I won’t lose any sleep over it. Until then documentation popups can be disabled… you just need to figure out they are the cause of the issue and be aware that there is a setting to disable them.

Or I could just use a custom build of wxWidgets for Code::Blocks... Oh wait, I already do.

My fix was committed to the development branch here. There is another commit that is enough to overcome this issue. It was committed to master here, and it was also backported to the WX_3_0_BRANCH here, so there is no need to backport my fix.

My fix was committed to the development branch here. There is another commit that fixes the issue. It was committed to master here, and it was also backported to the WX_3_0_BRANCH here.

Not sure. I've posted a question about that.

Seems like it. As you can see from the linked wxWidgets bug report, I've found the cause and also posted a patch. Also, another bug that was part of this crash has already been fixed since, and that effectively fixes this bug too.

Yes, I've reset all settings to default. Turns out the problem is indeed with the documentation popup which is a wxHtmlWindow. This widget tends to freeze programs if resized to some environment (and content etc.) specific size. So yes, it happens if you just move codeblocks to the right. I've tested on Ubuntu 18.04 which comes without Unity, and experienced the same bug. I've attached a small example for testing here: https://trac.wxwidgets.org/ticket/18141 I have given up digging deeper into wxHtmlWindow...

Yes, I've reset all settings to default. Turns out the problem is indeed with the documentation popup which is a wxHtmlWindow. This widget tends to freeze programs if resized to some environment (and content etc.) specific size. So yes, it happens if you just move codeblocks to the right. I've tested on Ubuntu 18.04 which comes without Unity, and experienced the same bug. I've attached a small example for testing here: https://trac.wxwidgets.org/ticket/18141 I have given up digging deeper into wxHtmlWindow...