Why does Code Blocks crash so many times on a Mac?

[jozemite]

Just downloaded it a few days ago and in the first 10 minutes of trying to learn it, it crashed over 4 times.

Just now it crashed about 5 times while changing the editor color, and once by adding a comment in my code. In fact, I just found out that it will crash 100% of the time I try changing the font.

What's up with that? Is reinstalling going to make it less buggy?

[oBFusCATed]

What's up with that? Is reinstalling going to make it less buggy?

Nope. The font changing is a known problem...

[ridge]

[Solved] Stop codeblocks from crashing on OSX.

1. Disable mis-behaving plugins.
In CodeBlocks: MenuBar->Plugins->Manage Plugins
Disable: Code completion, Keyboard shortcuts

2. Edit the codeblocks configuration file directly to change the font size.
(Don't use Settings->Editor to change the font size)
Note: CodeBlocks must not be running while you edit.
Edit ~/Library/Application Support/codeblocks/default.conf
Search for FONT
To change the font size from 10 to 12, change:
<![CDATA[0;10;75;90;90;0;Monaco;0]]>
to:
<![CDATA[0;12;75;90;90;0;Monaco;0]]>
Search for LOG_FONT_SIZE
To change the log font size, change 8 to something else:
<LOG_FONT_SIZE int="8" />
Now, start CodeBlocks to see how you like new font size settings.

[BlueHazzard]

just out of curiosity:

Nope. The font changing is a known problem...

is this a wxWidgets misbehavior but why then does this work?

(Don't use Settings->Editor to change the font size)
Note: CodeBlocks must not be running while you edit.
Edit ~/Library/Application Support/codeblocks/default.conf
Search for FONT
To change the font size from 10 to 12, change:
<![CDATA[0;10;75;90;90;0;Monaco;0]]>
to:
<![CDATA[0;12;75;90;90;0;Monaco;0]]>
Search for LOG_FONT_SIZE
To change the log font size, change 8 to something else:
<LOG_FONT_SIZE int="8" />
Now, start CodeBlocks to see how you like new font size settings.

[ridge]

There is a known problem and there is a work-around.
The problem won't be fixed until an OSX developer volunteer fixes it.
For now, you can use the work-around.

[BlueHazzard]

There is a known problem and there is a work-around.

Ok, but i would like to know where it crashes... Is it a problem with the font dialog? I have no mac, otherwise i would fire the debugger and look at a backtrace...

[oBFusCATed]

Yes, it is a problem with the font dialog in the wx2.8 on OSX. As far as I know this one is fixed for wx3.x.