User forums > Help
Code::Blocks Linux Stability Issues, Solutions?
Spirrwell:
Hello there.
For a long time through different distros Code::Blocks on Linux has always been really unstable for me, but it's much more stable now. I'm not experiencing complete crashes or a FLOOD of asserts.
Currently I'm using Code::Blocks with Manjaro 64 bit 17.0.4. The version of Code::Blocks is 16.01 rev 10692 (Built April 25, 2017) that I installed directly from Manjaro's software manager.
So it seems as though randomly after running Code::Blocks for a while, if I try to open a file in one of my projects, the text editor will just be blank, grey, and inactive. Though I can switch to other already open files with seemingly no problem. Sometimes when I go to do an action like left click then immediately right click at about the same time I will get an assert.
Quite often after this the GUI will begin to screw up and not have elements sized correctly like when I try to edit the build options of a project.
Also I don't believe this is related, but it seems like Code::Blocks does not recognize the platform specifc macros like __linux__ as you can see in the image above. It greys out what's inside the preprocessor, however this is purely visual, as the code still compiles as expected.
Essentially I want to know if others have experienced similar issues and if there's solutions beyond "waiting for a fix." Are the nightly builds any better? Would there be any difference if I built Code::Blocks myself? For the most part it functions normally, but these issues constantly happen and I have to close and re-open Code::Blocks to get back to normal state more often than not.
I'm not sure if I should file bug reports or not, as if I search, I tend to come across a lot of posts about crashing and bugs with Code::Blocks on Linux.
Regardless, any insight and help is appreciated
BlueHazzard:
Can you post what wxWidgets version you are using? You can get this information from the Help->About screen. Under the image there should be a line like "Build....... -wx2.8.12)...
It is probably a problem with the symbol browser. Try to disable it in the settings: Settings->Editor->code completion->Symbol browser->Disable symbol browser
Generally speaking the latest trunk version is the most stable version. So if you have the possibility to build codeblocks by yourself this would be the preferred way. Not long ago (1 month?) obfuscated fixed a lot crash and visual issues for ubuntu. Maybe this bug also affects you.
--- Quote ---Also I don't believe this is related, but it seems like Code::Blocks does not recognize the platform specifc macros like __linux__ as you can see in the image above. It greys out what's inside the preprocessor, however this is purely visual, as the code still compiles as expected.
--- End quote ---
I think this feature is not aware of the standard defines the compiler does, so it can not work properly for them (this is only a guess)...
oBFusCATed:
Try a night build. Most probably you'll have to build it yourself, but I guess finding a PKGBUILD file won't be that hard.
If the problem persists, please press the copy-to-clipboard button and paste the text here. Images aren't really useful.
Spirrwell:
Alright, so I went through the build process of the latest nightly. I cannot disable the symbol browser as it's simply greyed out in the settings:
I have not used it extensively yet, but I can still trigger an assert on demand by left clicking and immediately right clicking at about the same time. Here is a pastebin of the backtrace https://pastebin.com/8qbiMfDh
The version for wxWidgets is wx3.0.3. I guess I'll continue to use it and see if there's any other odd behavior, but it doesn't look promising.
oBFusCATed:
Yes, the symbol browser is disabled by default in now.
Can you post the exact steps required to reproduce the focus assert?
What happens if you press the ignore button instead of the stop button.
Most of the times the asserts generated by wx (this is one such assert) are not fatal.
Navigation
[0] Message Index
[#] Next page
Go to full version