Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Release 15.12, RC1 has arrived
Grabusz:
If by crash handler dialog you mean this dialog on the screenshot, then yes. Otherwise no. If yes - you have it's content in my previous post (it's the same every time).
It might be helpful - it seems that C::B is stuck somewhere waiting for something because windows won't realize that it stopped responding until I demand it to do something (for example switch focus to C::B window, or just click somewhere inside the window). It then goes white and... does nothing. The dialog from the screen shows once I press close button and wait for a while.
Yes I've tried waiting for an hour letting C::B do it's stuff, but the cpu usage was at 0%, and ram amount didn't change so I decided to terminate the process.
Btw, if you want me to collect some more data about this bug, tell me what to do because I have no idea on how to provide more info.
Oh, and on the screen C::B hang after opening typedefs.h (I opened my indexer.hpp file, then closed it, opened typedefs.h and program freezed).
And sorry for giving you a link to the screenshot, but it was too big (196kB) to send it as attachment.
oBFusCATed:
--- Quote from: Grabusz on January 01, 2016, 06:49:11 pm ---If by crash handler dialog you mean this dialog on the screenshot, then yes. Otherwise no. If yes - you have it's content in my previous post (it's the same every time).
--- End quote ---
This is not the crash handler dialog I have in mind. :(
Can someone else (running windows) try to reproduce the problem?
MortenMacFly:
--- Quote from: oBFusCATed on January 01, 2016, 07:02:32 pm ---Can someone else (running windows) try to reproduce the problem?
--- End quote ---
I tried hard but no issues here. Can you please try the following:
- download 15.xx-RC1
- install it somewhere
- do NOT run
- create an empty file "default.conf" in the installation folder
- run C::B
- configure the master path to you compiler
- close C::B
- open C::B, try to reproduce
Grabusz:
I've tried downloading 15.xx (both nightly builds and normal RC) using chrome and firefox, but every time my antivirust told me that the temp to which the file was being saved, was infected, thus I cannot download binaries now. So my question is - is there an option to revert c::b to the state it's after installation but before first run? Because I already have 13.12 and 15.12 RC1 installed, so I could just revert my 15.12 to right-after-installation state.
Before you ask - no, I don't have binaries on my hdd. I deleted them right after installation was completed :/
May I ask what creating an empty default.conf would cause? I mean, aren't all settings stored in the appdata?
And I got app's call stack while it's freezed, would that help in any way?
Some "more detailed" (yeah, it's sooooooo detailed :l ) info about the moment when C::B hangs:
It opens and loads the file, then switches focus to the newly created tab... aaaand then it hangs...
So... I'll post after I get binaries or learn how to compile C::B under windows.
headkase:
--- Quote from: Grabusz on January 01, 2016, 09:59:44 pm ---So my question is - is there an option to revert c::b to the state it's after installation but before first run? Because I already have 13.12 and 15.12 RC1 installed, so I could just revert my 15.12 to right-after-installation state.
--- End quote ---
Deleting the %APPDATA%\Roaming\CodeBlocks folder should be enough to restore it to a default state.
--- Quote from: Grabusz on January 01, 2016, 09:59:44 pm ---So... I'll post after I get binaries or learn how to compile C::B under windows.
--- End quote ---
Installing from source isn't terribly difficult: http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows
And if you don't want to go full-source you can always go nightly: http://wiki.codeblocks.org/index.php/Installing_Code::Blocks_nightly_build_on_Windows
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version