User forums > Help

CodeBlocks freezes during startup.

<< < (3/5) > >>

rickg22:
I supposed it *might* be a bug in wxwidgets regarding dialogs with 15bits color resolution, but it seems not.

Oh yeah. Mind posting a screenshot of the frozen C::B? And a try including the CPU usage (press ctrl-alt-del) so we can see the tasks.

Finally, as a workaround, try setting the blank_workspace to 1 and see if it doesn't freeze now.

adorlith:
 No luck with blank_workspace.

[attachment deleted by admin]

rickg22:
WEIRD! VERY WEIRD! It doesn't seem like it froze at all to me...

In the freeze that I experience, nothing is shown, just a white blank window. (This is getting more creepy everytime)

TDragon:
If you're looking for more startup freeze experiences, it's happening for me as well.

The symptoms:
1. codeblocks.exe is run.
2. The compiler auto-detection window appears. I click Close.
3. Nothing happens
4. Code::Blocks v1.0 appears on the taskbar, but clicking it does not bring it up and right-clicking has no effect
5. It appears as "Running" in the Applications tab of the Task Manager, with 00 CPU usage and about 14,900 k mem usage
6. It can be "artificially" shown by right-clicking in the Applications tab of the Task Manager and choosing "Maximize". The main window appears mostly as normal; however, it does not respond to anything.

My screenshots would be basically identical to adorlith's.

I conjecture it's freezing/pausing somewhere in wxWidgets. I'll try running it in GDB to find out where shortly.

adorlith:
  Here's the stack:
....................................................................................................................
(gdb) attach 7588                                                               
Attaching to program `D:\Utils\CodeBlocksRC2_debug\codeblocks.exe', process 7588
                                                                               
[Switching to thread 7588.0x145c]                                               
(gdb) where                                                                     
#0  0x7c901231 in wxscintilla_dll_iname ()                                     
#1  0x7c9507a8 in wxscintilla_dll_iname ()                                     
(gdb)                                                                           
.....................................................................................................................

Am I missing something ? I was expecting to see more function calls.

Navigation

[0] Message Index

[#] Next page

[*] Previous page