User forums > Using Code::Blocks
C::B crash after it wakes from hibernation
ollydbg:
Any one notice this crash issue?
I see such crash call stack:
--- Code: ---codeblocks.exe caused an Access Violation at location 0000000070A94BEC in module codeblocks.dll Reading from location 0000000000000000.
AddrPC Params
0000000070A94BEC 0000000006ADB440 0000000000000001 0000000000000014 codeblocks.dll!SurfaceD2D::InitPixMap
0000000070B62F26 0000000006CB7640 000000001665C9F0 0000000006A5F6A0 codeblocks.dll!EditView::RefreshPixMaps
0000000070B46A6B 0000000006CB7090 000000001665C9F0 000000000022ED20 codeblocks.dll!Editor::RefreshPixMaps
0000000070B46C64 0000000006CB7090 000000001665C9F0 0000000006CB7090 codeblocks.dll!Editor::Paint
0000000070A9DD66 0000000006CB7090 000000000022EE50 0000000070A8DF6C codeblocks.dll!ScintillaWX::DoPaint
0000000070A8DFE2 0000000006A5F6A0 000000000022F130 0000000000000000 codeblocks.dll!wxScintilla::OnPaint
0000000066A831B4 00000000009F0298 0000000077907B14 0000000000000003 wxmsw314u_gcc_cb.dll!wxAppConsoleBase::CallEventHandler
0000000066BDC1F2 000000000013076C 000007FEFAF7133C 000000000013076C wxmsw314u_gcc_cb.dll!wxEvtHandler::ProcessEventIfMatchesId
0000000066BDC3B7 0000000006A5F6A0 000000000013076C 000000000022F088 wxmsw314u_gcc_cb.dll!wxEventHashTable::HandleEvent
0000000066BDCA0D 000000000000000F 000000000022F4C8 0000000000000018 wxmsw314u_gcc_cb.dll!wxEvtHandler::TryHereOnly
0000000066BDCA7D 0000000000000085 0000000000000000 0000000022042B33 wxmsw314u_gcc_cb.dll!wxEvtHandler::ProcessEventLocally
0000000066BDCB61 0000000000000000 0000000000000000 0000000000000000 wxmsw314u_gcc_cb.dll!wxEvtHandler::ProcessEvent
0000000066BDE81B 000000000022F180 0000000006A5F6A0 0000000006A5F6A0 wxmsw314u_gcc_cb.dll!wxEvtHandler::SafelyProcessEvent
0000000066CE7CD5 0000000000000085 0000000000000001 0000000000000000 wxmsw314u_gcc_cb.dll!wxWindow::HandlePaint
0000000066CE973F 000000000005023A 000000000000000F 0000000000000000 wxmsw314u_gcc_cb.dll!wxWindow::MSWHandleMessage
0000000066CD91CC 0000000000000000 000000000022FA10 0000000000000001 wxmsw314u_gcc_cb.dll!wxWindow::MSWWindowProc
00000000777F8855 0000000000000000 0000000066CE1060 0000000000000000 USER32.dll!GetWindowDC
00000000777F7197 000000000000000F 0000000066B95470 00000000003A4B40 USER32.dll!SetWindowTextW
00000000777F66D9 0000000000000000 000000006764EF29 00000000000C0DCC USER32.dll!IsDialogMessageW
000000007794B5CF 00000000777F6D1C 0000000000000002 0000000000000000 ntdll.dll!KiUserCallbackDispatcher
00000000777F6D0A 0000000000000002 0000000000000000 0000000000000000 USER32.dll!BeginPaint
00000000777F6D1C 0000000000000000 0000000000000000 0000000066CE1060 USER32.dll!BeginPaint
00000000777F6672 0000000006A474E0 00000000777F7DF2 00000000FFFFFFEC USER32.dll!IsDialogMessageW
0000000066CDBBAB 00000000068E2170 0000000066D2321B 00000000068E2190 wxmsw314u_gcc_cb.dll!wxWindow::MSWSafeIsDialogMessage
0000000066CDBDF9 0000000006A5F6A0 0000000000000001 00000000777F8F6A wxmsw314u_gcc_cb.dll!wxWindow::MSWProcessMessage
0000000066D0999A 000000000000000F 0000000000000000 0000000000000000 wxmsw314u_gcc_cb.dll!wxGUIEventLoop::PreProcessMessage
0000000066D09861 00000000003A4B40 0000000066A853FF 0000000066CE1060 wxmsw314u_gcc_cb.dll!wxGUIEventLoop::ProcessMessage
0000000066D09676 00000000068E2170 000000000000000F 0000000000000000 wxmsw314u_gcc_cb.dll!wxGUIEventLoop::Dispatch
0000000066AB6523 00000000068E2170 000007FEFF9513D2 0000000000000002 wxmsw314u_gcc_cb.dll!wxEventLoopManual::ProcessEvents
0000000066AB660E 00000000003A4B40 00000000068E2170 0000000000000048 wxmsw314u_gcc_cb.dll!wxEventLoopManual::DoRun
0000000066AB6279 00000000068EA5A0 000000020000001C 00000000068E2170 wxmsw314u_gcc_cb.dll!wxEventLoopBase::Run
0000000066A8719A 000000000000001E 0000000000000009 000000000022FD30 wxmsw314u_gcc_cb.dll!wxAppConsoleBase::MainLoop
0000000000405808 00000000003A4B40 0000000066BE944B 000000000036ADA0 codeblocks.exe!0x5808
0000000066AFEB95 0000000000000048 0000000000000006 000000000036ADA0 wxmsw314u_gcc_cb.dll!wxInitialize
000000000040255B 0000000000400000 0000000000000000 00000000007535F2 codeblocks.exe!0x255b
00000000004013C7 0000000000000000 0000000000000000 0000000000000000 codeblocks.exe!0x13c7
00000000004014CB 0000000000000000 0000000000000000 0000000000000000 codeblocks.exe!0x14cb
00000000776D556D 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!BaseThreadInitThunk
000000007793385D 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!RtlUserThreadStart
--- End code ---
It looks like after this crash, C::B try to connect some internet address IP(204.79.197.219, sounds like a MS cloud server IP), this is detected my network firewall (https://github.com/henrypp/simplewall)
Miguel Gimenez:
The connection is made by Windows itself trying to send a crash report.
Hibernation has caused a lot of problems on Windows, specially with flaky drivers. This may be a problem in C::B, but I think it is related to your graphic card driver not restoring the D2D surface properly.
ollydbg:
Thanks for the reply.
--- Quote from: Miguel Gimenez on December 05, 2020, 01:01:03 pm ---The connection is made by Windows itself trying to send a crash report.
Hibernation has caused a lot of problems on Windows, specially with flaky drivers. This may be a problem in C::B, but I think it is related to your graphic card driver not restoring the D2D surface properly.
--- End quote ---
I think you are right.
I never see it crashed if I don't enable the "Ligature feature" of the editor.
I think I have install the latest Intel HD graphics card's driver in my notebook.
ollydbg:
I think it maybe a C::B bug, because I can reproduce this crash on two PCs, call-stacks show that all are related to direct2d calls.
But they have different graphics cards.
EDIT:
I found that not only hibernation will crash the crash, but just lock the screen and login will cause crash too.
stahta01:
Do you have an project open when the problem happens?
Do you have an file open in the editor when the problem happens?
What windows version?
Tim S.
Navigation
[0] Message Index
[#] Next page
Go to full version