Author Topic: Release 15.12, RC1 has arrived  (Read 28435 times)

Offline Grabusz

  • Multiple posting newcomer
  • *
  • Posts: 15
Re: Release 15.12, RC1 has arrived
« Reply #60 on: December 31, 2015, 01:39:00 pm »
1.When you open one (or more) files, there's a chance that C::B will hang after opening it. You will have to just kill the process, and start again... It took me 5 times to load all files I needed this time (it's not yet a project. I'm just testing something). And it's not just a recent bug, because it also occurs in 13.12.
Can you share a file that will cause cb to crash?

Started C::B and then File -> Recent Files -> typedefs.h and then doing File -> Recent Files -> reference.hpp freezed the program (opening through File -> Open... seems to freeze program less frequently).

2. It would be nice if C::B would create new empty file when you double-clicked on the tab bar with file names. (or maybe it already was implemented and it's somewhere in menu and I didn't find it?)
ctrl-shift-n or file -> new -> empty file

I am aware of that (I even changed ctrl+shift+n to ctrl+n) but still it doesn't change the fact that it would be nice :)
And sometimes it's just faster :)

5. C++ Parser hangs or just doing his job way too long, because sometimes it displays that popup (floating box? text? w/e) that it's still parsing files for more than an hour... in a project that includes 4 standard libraries and 5 small files.
Share a project which can be used to reproduce the problem, please.

It's a randomly occuring thing, and I will post you everything as soon as it happens again.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12022
    • Travis build status
Re: Release 15.12, RC1 has arrived
« Reply #61 on: December 31, 2015, 01:42:50 pm »
I am aware of that (I even changed ctrl+shift+n to ctrl+n) but still it doesn't change the fact that it would be nice :)
And sometimes it's just faster :)
Double clicking on the tab bar switches to the minimal perspective, so this is already used for something else.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12022
    • Travis build status
Re: Release 15.12, RC1 has arrived
« Reply #62 on: December 31, 2015, 01:48:09 pm »
Started C::B and then File -> Recent Files -> typedefs.h and then doing File -> Recent Files -> reference.hpp freezed the program (opening through File -> Open... seems to freeze program less frequently).
Didn't cause a crash here - rev10637, wx30, gentoo linux.
Does it crash every time or it is some random event?

Does it crash if you disable the code completion plugin?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Grabusz

  • Multiple posting newcomer
  • *
  • Posts: 15
Re: Release 15.12, RC1 has arrived
« Reply #63 on: December 31, 2015, 02:09:19 pm »
Started C::B and then File -> Recent Files -> typedefs.h and then doing File -> Recent Files -> reference.hpp freezed the program (opening through File -> Open... seems to freeze program less frequently).
Didn't cause a crash here - rev10637, wx30, gentoo linux.
Does it crash every time or it is some random event?

Does it crash if you disable the code completion plugin?

Sadly it's a random event, but the chance it will occur is high enough to annoy me.

I'll disable code completion plugin and edit this post (except told otherwise) if it worked.

I'm using both
15.12 rev 10596 and
13.12 rev 9501
on 64-bit Windows 7
____________________________

Edit: Hanged on the first try :/

Problem details:
Quote
  Problem Event Name:   AppHangB1
  Application Name:   codeblocks.exe
  Application Version:   13.12.0.0
  Application Timestamp:   00000000
  Hang Signature:   2db8
  Hang Type:   0
  Additional Hang Signature 1:   2db8e61ac06ad6d7fa4d8409c314654f
  Additional Hang Signature 2:   2372
  Additional Hang Signature 3:   2372cbe6818f95cdc639c00feddd87e6
  Additional Hang Signature 4:   2db8
  Additional Hang Signature 5:   2db8e61ac06ad6d7fa4d8409c314654f
  Additional Hang Signature 6:   2372
  Additional Hang Signature 7:   2372cbe6818f95cdc639c00feddd87e6

Maybe it will help (it's 15.12, but I also have 13.12 installed, and I guess that old version number is in the registry or something).
« Last Edit: December 31, 2015, 03:05:10 pm by Grabusz »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12022
    • Travis build status
Re: Release 15.12, RC1 has arrived
« Reply #64 on: January 01, 2016, 02:40:49 pm »
Do you see a crash handler dialog which allows you to save some info about the crash?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Grabusz

  • Multiple posting newcomer
  • *
  • Posts: 15
Re: Release 15.12, RC1 has arrived
« Reply #65 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).

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.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12022
    • Travis build status
Re: Release 15.12, RC1 has arrived
« Reply #66 on: January 01, 2016, 07:02:32 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).
This is not the crash handler dialog I have in mind. :(

Can someone else (running windows) try to reproduce the problem?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: Release 15.12, RC1 has arrived
« Reply #67 on: January 01, 2016, 08:01:51 pm »
Can someone else (running windows) try to reproduce the problem?
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
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Grabusz

  • Multiple posting newcomer
  • *
  • Posts: 15
Re: Release 15.12, RC1 has arrived
« Reply #68 on: January 01, 2016, 09:59:44 pm »
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.

Offline headkase

  • Almost regular
  • **
  • Posts: 159
Re: Release 15.12, RC1 has arrived
« Reply #69 on: January 01, 2016, 10:03: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.

Deleting the %APPDATA%\Roaming\CodeBlocks folder should be enough to restore it to a default state.

So... I'll post after I get binaries or learn how to compile C::B under windows.

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

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12022
    • Travis build status
Re: Release 15.12, RC1 has arrived
« Reply #70 on: January 01, 2016, 10:30:46 pm »
And I got app's call stack while it's freezed, would that help in any way?
It might help if there are function names in it. Post it and we will tell you.

default.conf and any other conf file is stored somewhere (CodeBlocks folder) in %AppData%.
Delete this folder and you'll be in a state just-like-after-installation.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Grabusz

  • Multiple posting newcomer
  • *
  • Posts: 15
Re: Release 15.12, RC1 has arrived
« Reply #71 on: January 02, 2016, 05:32:10 am »
Here's the call stack:

Code: [Select]
ntoskrnl.exe!memset+0x64a
ntoskrnl.exe!KeWaitForMultipleObjects+0xd52
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PoStartNextPowerIrp+0xbb4
ntoskrnl.exe!PoStartNextPowerIrp+0x185d
ntoskrnl.exe!KeWaitForMultipleObjects+0xf5d
ntoskrnl.exe!KeDelayExecutionThread+0x186
ntoskrnl.exe!NtWaitForSingleObject+0x16e
ntoskrnl.exe!KeSynchronizeExecution+0x3a23
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x56b
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x42a
ntdll.dll!RtlUniform+0x6e6
ntdll.dll!EtwEventSetInformation+0x1d7bd
ntdll.dll!LdrInitializeThunk+0xe
ntdll.dll!ZwDelayExecution+0x15
KERNELBASE.dll!Sleep+0xf
wxmsw28u_gcc_cb.dll!_Z9wxExecuteRK8wxStringiP9wxProcess+0xdfe
wxmsw28u_gcc_cb.dll!_ZN15wxMessageOutput3SetEPS_+0x407
codecompletion.dll+0x54a64
codecompletion.dll+0x54d8c
codecompletion.dll+0x56cd8
codecompletion.dll+0x57490
codecompletion.dll+0x57c82
codecompletion.dll+0x234d6
wxmsw28u_gcc_cb.dll!_ZNK12wxAppConsole11HandleEventEP12wxEvtHandlerMS0_FvR7wxEventES3_+0x22
wxmsw28u_gcc_cb.dll!_ZN11wxTimerBase6NotifyEv+0x9b
wxmsw28u_gcc_cb.dll!_ZN7wxTimer4InitEv+0xab
USER32.dll!gapfnScSendMessage+0x270
USER32.dll!gapfnScSendMessage+0x922
USER32.dll!LoadStringW+0x11f
USER32.dll!DispatchMessageW+0xf
USER32.dll!IsDialogMessageW+0x11e
wxmsw28u_gcc_cb.dll!_ZN11wxEventLoop17PreProcessMessageEP6tagMSG+0xac
wxmsw28u_gcc_cb.dll!_ZN11wxEventLoop8DispatchEv+0x11d
wxmsw28u_gcc_cb.dll!_ZN5wxApp5YieldEb+0xa9
wxmsw28u_gcc_cb.dll!_Z7wxYieldv+0x1e
wxmsw28u_gcc_cb.dll!_ZN15wxMessageOutput3SetEPS_+0x407
codecompletion.dll+0x553a4
codecompletion.dll+0x5607a
codecompletion.dll+0x5647b
codecompletion.dll+0x56b75
codecompletion.dll+0x56cab
codecompletion.dll+0x57490
codecompletion.dll+0x57c82
codecompletion.dll+0x234d6
wxmsw28u_gcc_cb.dll!_ZNK12wxAppConsole11HandleEventEP12wxEvtHandlerMS0_FvR7wxEventES3_+0x22
wxmsw28u_gcc_cb.dll!_ZN11wxTimerBase6NotifyEv+0x9b
wxmsw28u_gcc_cb.dll!_ZN7wxTimer4InitEv+0xab
USER32.dll!gapfnScSendMessage+0x270
USER32.dll!gapfnScSendMessage+0x922
USER32.dll!LoadStringW+0x11f
USER32.dll!DispatchMessageW+0xf
USER32.dll!IsDialogMessageW+0x11e
wxmsw28u_gcc_cb.dll!_ZN11wxEventLoop17PreProcessMessageEP6tagMSG+0xac
wxmsw28u_gcc_cb.dll!_ZN11wxEventLoop8DispatchEv+0x11d
wxmsw28u_gcc_cb.dll!_ZN17wxEventLoopManual3RunEv+0x128

Tomorrow I will delete the C::B folder in appdata, and see if it will solve the problem

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12022
    • Travis build status
Re: Release 15.12, RC1 has arrived
« Reply #72 on: January 02, 2016, 12:16:45 pm »
It looks like it crashes in the code-completion plugin, but the backtrace is garbled, because the CC plugin is never calling wxMessageOutput as far as I can see.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Grabusz

  • Multiple posting newcomer
  • *
  • Posts: 15
Re: Release 15.12, RC1 has arrived
« Reply #73 on: January 03, 2016, 10:22:40 am »
So... First i tried to turn off Code Completion and see if the call stack changes... it was exactly the same, so I guess it's corrupted.

After renaming CodeBlocks folder in Roaming and creating blank default.conf in the main dir the problem disappeared, and after reverting to my old settings it was back... so I guess it's caused by my settings... do you want me to upload my zipped %appdata%\CodeBlocks so you could examine it or should I just erase all my settings and start everything anew?

Here's something I think is worth mentioning - when I'm on my settings and open a file the c::b refreshes it's UI many times (and it's so slow that it takes about 0.5-1.2s), but after i load default settings, the process takes less than 0.3s and is barely visible.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: Release 15.12, RC1 has arrived
« Reply #74 on: January 03, 2016, 10:38:54 am »
May I ask what creating an empty default.conf would cause? I mean, aren't all settings stored in the appdata?
It makes C::B portable and ensures that:
- its like plain new, after a fresh installation
- no other settings interfere with this version

-> I wanted to have a clean version.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ