Author Topic: Crashes anyone??  (Read 13140 times)

Offline daniloz

  • Regular
  • ***
  • Posts: 268
Re: Crashes anyone??
« Reply #15 on: December 13, 2010, 12:30:52 pm »
I am using rev6883 for a few days and same... it crashes or freezes about once every two days of so, but I can also have two or three freezes per day on some "bad days"... :-)

Please let me know can I help further here...

Btw, I rolled back to wv2.8.10 and still the same...

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: Crashes anyone??
« Reply #16 on: December 14, 2010, 02:59:27 pm »
I am using rev6883 for a few days and same... it crashes or freezes about once every two days of so, but I can also have two or three freezes per day on some "bad days"... :-)

Please let me know can I help further here...

Btw, I rolled back to wv2.8.10 and still the same...
I can't reproduce, sorry.

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: Crashes anyone??
« Reply #17 on: December 15, 2010, 05:46:12 am »
Maybe, just maybe, this patch can fix the crash. :P
Please have a trying?
« Last Edit: December 20, 2010, 01:25:19 pm by Loaden »

Offline daniloz

  • Regular
  • ***
  • Posts: 268
Re: Crashes anyone??
« Reply #18 on: December 15, 2010, 08:21:41 am »
@Loaden:

Thank you for the patch, I have applied it and will report feedback soon...

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Crashes anyone??
« Reply #19 on: December 15, 2010, 09:12:09 am »
Loaded: My crashes are in the Parse/Token classes/files. Not in the GUI.
Unfortunately the last time I've got a crash, copying the backtrace failed :(
(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 ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5919
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Crashes anyone??
« Reply #20 on: December 15, 2010, 10:03:57 am »
Loaded: My crashes are in the Parse/Token classes/files. Not in the GUI.
Unfortunately the last time I've got a crash, copying the backtrace failed :(
it is too hard to catch this kind of bug,because people use different code to be parsed. i am always thinking a good test case which can help us to find the crashes in the parser...
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: Crashes anyone??
« Reply #21 on: December 15, 2010, 10:04:56 am »
Loaded: My crashes are in the Parse/Token classes/files. Not in the GUI.
Unfortunately the last time I've got a crash, copying the backtrace failed :(
No, The GUI crash occured with wx-2.9 always.
This patch can avoid CC crash when use wx-2.9.2svn.

update to V2.
« Last Edit: December 20, 2010, 01:24:50 pm by Loaden »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Crashes anyone??
« Reply #22 on: December 15, 2010, 12:19:40 pm »
it is too hard to catch this kind of bug,because people use different code to be parsed. i am always thinking a good test case which can help us to find the crashes in the parser...
The thing is that this crash happens during typing and it is very rare...
So, probably some invalid code triggers it.
« Last Edit: December 15, 2010, 12:24:17 pm by oBFusCATed »
(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 Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: Crashes anyone??
« Reply #23 on: December 15, 2010, 12:51:02 pm »
it is too hard to catch this kind of bug,because people use different code to be parsed. i am always thinking a good test case which can help us to find the crashes in the parser...
The thing is that this crash happens during typing and it is very rare...
So, probably some invalid code triggers it.
If you disable class browser, the crash or freeze should gone.
At least in here, it only happened in ClassBrowser.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Crashes anyone??
« Reply #24 on: December 15, 2010, 01:32:09 pm »
I'm running with wx-2.8.11, not wx-2.9.1 and the crash is not related to the class browser!
(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 daniloz

  • Regular
  • ***
  • Posts: 268
Re: Crashes anyone??
« Reply #25 on: December 20, 2010, 12:34:29 pm »
One more crash here, while using rev6900, wx-2.8.10, Vista 32bit... it happened when I closed the CodeBlocks project, while having 4 other projects in the Workspace, after a successful build...

Here is the RPT file:
Code
Error occured on Monday, December 20, 2010 at 12:20:54.

C:\Work\codeblocks_trunk\src\output\codeblocks.exe caused an Access Violation at location 65e9ba95 in module C:\Work\codeblocks_trunk\src\output\share\codeblocks\plugins\codecompletion.dll Reading from location 1aef2dc8.

Registers:
eax=1aef2d90 ebx=00000000 ecx=77749c10 edx=006ffefc esi=00000431 edi=0022e6d8
eip=65e9ba95 esp=0022e208 ebp=0022e300 iopl=0         nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010246

Call stack:
65E9BA95  C:\Work\codeblocks_trunk\src\output\share\codeblocks\plugins\codecompletion.dll:65E9BA95
C:/Work/codeblocks_trunk/src/plugins/codecompletion/classbrowserbuilderthread.cpp:804

65E9D7E2  C:\Work\codeblocks_trunk\src\output\share\codeblocks\plugins\codecompletion.dll:65E9D7E2
C:/Work/codeblocks_trunk/src/plugins/codecompletion/classbrowserbuilderthread.cpp:1002

65E9827A  C:\Work\codeblocks_trunk\src\output\share\codeblocks\plugins\codecompletion.dll:65E9827A
C:/Work/codeblocks_trunk/src/plugins/codecompletion/classbrowser.cpp:781

62783C28  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:62783C28  _ZN12wxEvtHandler21ProcessEventIfMatchesERK21wxEventTableEntryBasePS_R7wxEvent
62783D61  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:62783D61  _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler
6278412C  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:6278412C  _ZN12wxEvtHandler12ProcessEventER7wxEvent
6289232F  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:6289232F  _ZN12wxWindowBase9TryParentER7wxEvent
6289232F  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:6289232F  _ZN12wxWindowBase9TryParentER7wxEvent
6289232F  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:6289232F  _ZN12wxWindowBase9TryParentER7wxEvent
6281D58D  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:6281D58D  _ZN10wxTreeCtrl11MSWOnNotifyEilPl
627D1A02  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:627D1A02  _ZN8wxWindow13MSWWindowProcEjjl
627CB6FE  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:627CB6FE  _Z9wxWndProcP6HWND__jjl@16
77ECFD72  C:\Windows\system32\USER32.dll:77ECFD72  GetWindowLongW
77ECFE4A  C:\Windows\system32\USER32.dll:77ECFE4A  GetWindowLongW
77EC9D6A  C:\Windows\system32\USER32.dll:77EC9D6A  ReleaseDC
77EC9F8D  C:\Windows\system32\USER32.dll:77EC9F8D  WCSToMBEx
77D55DAE  C:\Windows\system32\ntdll.dll:77D55DAE  KiUserCallbackDispatcher
77ED0B36  C:\Windows\system32\USER32.dll:77ED0B36  SendMessageW
74EC70E2  C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18005_none_5cb72f96088b0de0\COMCTL32.DLL:74EC70E2  DSA_SetItem
74EC26F6  C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18005_none_5cb72f96088b0de0\COMCTL32.DLL:74EC26F6  ImageList_GetBkColor
74EC24E8  C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18005_none_5cb72f96088b0de0\COMCTL32.DLL:74EC24E8  ImageList_GetBkColor
74EDD8BD  C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18005_none_5cb72f96088b0de0\COMCTL32.DLL:74EDD8BD  _TrackMouseEvent
74F3017A  C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18005_none_5cb72f96088b0de0\COMCTL32.DLL:74F3017A  ImageList_SetBkColor
74F29D33  C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18005_none_5cb72f96088b0de0\COMCTL32.DLL:74F29D33  ImageList_Draw
77ECFD72  C:\Windows\system32\USER32.dll:77ECFD72  GetWindowLongW
77ECFE4A  C:\Windows\system32\USER32.dll:77ECFE4A  GetWindowLongW
77ED09D3  C:\Windows\system32\USER32.dll:77ED09D3  CallWindowProcW
77ED0979  C:\Windows\system32\USER32.dll:77ED0979  CallWindowProcW
627C81BA  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:627C81BA  _ZN8wxWindow16MSWDefWindowProcEjjl
627D14D3  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:627D14D3  _ZN8wxWindow13MSWWindowProcEjjl
6281E90F  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:6281E90F  _ZN10wxTreeCtrl13MSWWindowProcEjjl
627CB6FE  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:627CB6FE  _Z9wxWndProcP6HWND__jjl@16
77ECFD72  C:\Windows\system32\USER32.dll:77ECFD72  GetWindowLongW
77ECFE4A  C:\Windows\system32\USER32.dll:77ECFE4A  GetWindowLongW
77EC9D6A  C:\Windows\system32\USER32.dll:77EC9D6A  ReleaseDC
77EC9F8D  C:\Windows\system32\USER32.dll:77EC9F8D  WCSToMBEx
77D55DAE  C:\Windows\system32\ntdll.dll:77D55DAE  KiUserCallbackDispatcher
627B0A7E  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:627B0A7E  _ZN11wxEventLoop8DispatchEv
62844A6C  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:62844A6C  _ZN17wxEventLoopManual3RunEv
62824279  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:62824279  _ZN9wxAppBase8MainLoopEv
004058C4  C:\Work\codeblocks_trunk\src\output\codeblocks.exe:004058C4
6273114E  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:6273114E  _Z14wxEntryCleanupv
627895D6  C:\Work\codeblocks_trunk\src\output\wxmsw28u_gcc_custom.dll:627895D6  _Z7wxEntryP11HINSTANCE__S0_Pci
00401D71  C:\Work\codeblocks_trunk\src\output\codeblocks.exe:00401D71  WinMain@16  C:/Work/codeblocks_trunk/src/src/app.cpp:260
0045F246  C:\Work\codeblocks_trunk\src\output\codeblocks.exe:0045F246
004010DB  C:\Work\codeblocks_trunk\src\output\codeblocks.exe:004010DB
00401158  C:\Work\codeblocks_trunk\src\output\codeblocks.exe:00401158
768ED0E9  C:\Windows\system32\kernel32.dll:768ED0E9  BaseThreadInitThunk
77D319BB  C:\Windows\system32\ntdll.dll:77D319BB  RtlInitializeExceptionChain
77D3198E  C:\Windows\system32\ntdll.dll:77D3198E  RtlInitializeExceptionChain

@loaden:
is your commit at rev6901 (" fix a bug in ClassBrowser, avoid duplication refresh") solves this issue ??

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Re: Crashes anyone??
« Reply #26 on: December 20, 2010, 12:54:29 pm »
The r6901 commit not related with this issue.
And have a question, whether there is a clean code? not applied any patch ?

Offline daniloz

  • Regular
  • ***
  • Posts: 268
Re: Crashes anyone??
« Reply #27 on: December 20, 2010, 01:12:55 pm »
The r6901 commit not related with this issue.
And have a question, whether there is a clean code? not applied any patch ?
Yes, no patches applied... since I though that your patches only apply for wx-2.9, right?