Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Release 15.12, RC1 has arrived

<< < (15/19) > >>

oBFusCATed:

--- Quote from: Grabusz on January 01, 2016, 09:59:44 pm ---And I got app's call stack while it's freezed, would that help in any way?

--- End quote ---
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.

Grabusz:
Here's the call stack:


--- Code: ---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

--- End code ---

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

oBFusCATed:
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.

Grabusz:
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.

MortenMacFly:

--- Quote from: Grabusz on January 01, 2016, 09:59:44 pm ---May I ask what creating an empty default.conf would cause? I mean, aren't all settings stored in the appdata?

--- End quote ---
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page