Posted April 6, 2007 CRASHED FIRST TIME AND THAT TO THRICE IN 2DAYS I WAS WORKING NORMALLY ON THE CLIENT WHEN IT CRASHED. SINCE INSTALL 8MTHS BACK IT HAS CRASHED FOR THE FIRST TIME. ALSO AFTER THE CRASH MY FAVOURITE HUBLIST HAS BEEN MISSING AND CANNOT BE RESTORED. BELOW ARE THE THREE CRASH REPORTS Code: c0000005 (Access violation) Version: 0.4.0 (2006-12-24) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-04-05 17:54:12 TTH: BHXJ5QVCTZZBW4F4FFVZQOOSP6T2BAVNHS75OQQ d:\cvs\apexdc++\includes\stlport\stlport\stl\_tree.c(298): stlp_std::priv::_Rb_global<bool>::_M_increment d:\cvs\apexdc++\apexdc\client\user.cpp(41): Identity::getParams d:\cvs\apexdc++\apexdc\windows\hubframe.cpp(1276): HubFrame::addLine d:\cvs\apexdc++\apexdc\windows\hubframe.cpp(1259): HubFrame::addLine d:\cvs\apexdc++\apexdc\windows\hubframe.cpp(2213): HubFrame::addClientLine d:\cvs\apexdc++\apexdc\windows\hubframe.cpp(820): HubFrame::onSpeaker d:\cvs\apexdc++\apexdc\windows\hubframe.h(75): HubFrame::ProcessWindowMessage d:\program files\microsoft visual studio 8\vc\atlmfc\include\atlwin.h(3078): ATL::CWindowImplBaseT<WTL::CMDIWindow=0x02DCF678,ATL::CWinTraits<1456406528=0x00000000,64> >::WindowProc USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E4189CD: GetWindowLongW USER32!0x7E418A10: DispatchMessageW d:\cvs\apexdc++\includes\wtl\atlapp.h(584): WTL::CMessageLoop::Run d:\cvs\apexdc++\apexdc\windows\main.cpp(429): Run 0x00050110: ? ApexDC!0x0044A10F: MainFrame::FileListQueue::`scalar deleting destructor' ApexDC!0x004661CA: [thunk]:MainFrame::`vector deleting destructor' 0x8351F8E4: ? Code: c0000094 (Integer division by zero) Version: 0.4.0 (2006-12-24) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-04-06 21:45:23 TTH: BHXJ5QVCTZZBW4F4FFVZQOOSP6T2BAVNHS75OQQ F:\RTM\vctools\crt_bld\SELF_X86\crt\src\intel\lldiv.asm(120): _alldiv d:\cvs\apexdc++\apexdc\windows\transferview.h(61): TransferView::ProcessWindowMessage d:\program files\microsoft visual studio 8\vc\atlmfc\include\atlwin.h(3078): ATL::CWindowImplBaseT<WTL::CTreeViewCtrlT<ATL::CWindow>=0x0012FA0C,ATL::CWinTraits<1442840576=0x00000000,0> >::WindowProc USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E41B89B: GetParent USER32!0x7E41B903: SendMessageW COMCTL32!0x773EAFF1: Ordinal414 COMCTL32!0x773EB07F: Ordinal341 COMCTL32!0x7743CBA7: Ordinal384 COMCTL32!0x77417F04: Ordinal384 COMCTL32!0x7741DD04: Ordinal384 COMCTL32!0x7741ECAA: Ordinal384 COMCTL32!0x774215BE: Ordinal384 USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E41C63F: IsWindowUnicode USER32!0x7E41C665: CallWindowProcW d:\program files\microsoft visual studio 8\vc\atlmfc\include\atlwin.h(3081): ATL::CWindowImplBaseT<WTL::CTreeViewCtrlT<ATL::CWindow>=0x0012FA68,ATL::CWinTraits<1442840576=0x00000000,0> >::WindowProc USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E41B4C0: DefWindowProcW USER32!0x7E41B50C: DefWindowProcW ntdll!0x7C90EAE3: KiUserCallbackDispatcher USER32!0x7E418A10: DispatchMessageW d:\cvs\apexdc++\includes\wtl\atlapp.h(584): WTL::CMessageLoop::Run d:\cvs\apexdc++\apexdc\windows\main.cpp(429): Run 0x000900E6: ? ApexDC!0x0044A10F: MainFrame::FileListQueue::`scalar deleting destructor' ApexDC!0x004661CA: [thunk]:MainFrame::`vector deleting destructor' 0x8351F8E4: ? Code: c0000094 (Integer division by zero) Version: 0.4.0 (2006-12-24) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-04-06 23:02:51 TTH: BHXJ5QVCTZZBW4F4FFVZQOOSP6T2BAVNHS75OQQ F:\RTM\vctools\crt_bld\SELF_X86\crt\src\intel\lldiv.asm(120): _alldiv d:\cvs\apexdc++\apexdc\windows\transferview.h(61): TransferView::ProcessWindowMessage d:\program files\microsoft visual studio 8\vc\atlmfc\include\atlwin.h(3078): ATL::CWindowImplBaseT<WTL::CTreeViewCtrlT<ATL::CWindow>=0x0012FA0C,ATL::CWinTraits<1442840576=0x00000000,0> >::WindowProc USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E41B89B: GetParent USER32!0x7E41B903: SendMessageW COMCTL32!0x773EAFF1: Ordinal414 COMCTL32!0x773EB07F: Ordinal341 COMCTL32!0x7743CBA7: Ordinal384 COMCTL32!0x77417F04: Ordinal384 COMCTL32!0x7741DD04: Ordinal384 COMCTL32!0x7741ECAA: Ordinal384 COMCTL32!0x774215BE: Ordinal384 USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E41C63F: IsWindowUnicode USER32!0x7E41C665: CallWindowProcW d:\program files\microsoft visual studio 8\vc\atlmfc\include\atlwin.h(3081): ATL::CWindowImplBaseT<WTL::CTreeViewCtrlT<ATL::CWindow>=0x0012FA68,ATL::CWinTraits<1442840576=0x00000000,0> >::WindowProc USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E41B4C0: DefWindowProcW USER32!0x7E41B50C: DefWindowProcW ntdll!0x7C90EAE3: KiUserCallbackDispatcher USER32!0x7E418A10: DispatchMessageW d:\cvs\apexdc++\includes\wtl\atlapp.h(584): WTL::CMessageLoop::Run d:\cvs\apexdc++\apexdc\windows\main.cpp(429): Run 0x001A0538: ? ApexDC!0x0044A10F: MainFrame::FileListQueue::`scalar deleting destructor' ApexDC!0x004661CA: [thunk]:MainFrame::`vector deleting destructor' 0x8351F8E4: ? Share this post Link to post Share on other sites
Posted April 6, 2007 WELL LET ME TELL YOU SOMETHING I FEEL. TODAY WHEN I RETURNED FROM GOOD FRIDAY, I STARTED MY CLIENT ONLY TO FIND THAT SOME techgeeks.geekgalaxy.com:1411 opened AUTOMATICALLY. ALSO MY FAVOURITE HUBS HAVE DISAPPEARED. AND MY CLIENT CRASHED FOR THE SECOND TIME SOME SAMARITAN NAMED TEOBALD DIRECTED ME HERE WHEN I SHOWED HIM THE CRASH REPORT. ON RECONNECTING THE CLIENT AND RESTORING MY FAVOURITE HUBS I FOUND ALL WELL BUT WHEN THAT TECH GEEK GOT CONNECTED MY CLIENT CRASHED AGAIN. MY CLIENT HAS NEVER CRASHED ON JOINING OTHER HUBS. THE FIRST TIME IT CRASHED I DONT REMEMBER THE REASON OF WHAT I WAS DOIN Share this post Link to post Share on other sites
Posted April 7, 2007 Is someone going to reply . . . plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz Share this post Link to post Share on other sites
Posted April 7, 2007 Sorry for the delay in a reply, I just guess no one was around at the time. Anyway, I cannot tell you myself what the cause of your crash was, hopefully Crise will be able to tell us a bit more when he sees this. Until then I've just edited your post to put the reports in code tags, so they'll be a little easier to read. I seem to get the impression you keep a backup of your favorites XML file... good idea. Thanks you very much for reporting the crashes and posting the crash reports. Sorry I can't be of anymore help for the moment, hopefully someone who can be of more assistance will see this thread soon. Share this post Link to post Share on other sites
Posted April 7, 2007 Sorry for the delay in a reply, I just guess no one was around at the time. Anyway, I cannot tell you myself what the cause of your crash was, hopefully Crise will be able to tell us a bit more when he sees this. Until then I've just edited your post to put the reports in code tags, so they'll be a little easier to read. I seem to get the impression you keep a backup of your favorites XML file... good idea. Thanks you very much for reporting the crashes and posting the crash reports. Sorry I can't be of anymore help for the moment, hopefully someone who can be of more assistance will see this thread soon. Thanks , But a mate named OP Aryana aid that it was some coding error so i reinstalled it . lets see if it gives trouble again By the way my whole apex folder is backed :[) Share this post Link to post Share on other sites
Posted April 7, 2007 Bugs and crashes are caused by coding errors, your 'new' apex is the same as the old one (i admit that maybe it'll work better with your new settings though) Devs will now look through your crash report, they will try to find the root cause and fix it. If they succeed this will be fixed (if not already) in the next release. So please be patient :) Share this post Link to post Share on other sites
Posted April 7, 2007 Yes, this is just the usual way, bug reports are posted and fixed ASAP with a new release on the fly, in 90% of the cases there is not much that the user can do. But everything is read carefully, be sure. And I dare to advise nobody to advise users to reinstall just for the sport. :) Share this post Link to post Share on other sites
Posted April 10, 2007 Yes, this is just the usual way, bug reports are posted and fixed ASAP with a new release on the fly, in 90% of the cases there is not much that the user can do. But everything is read carefully, be sure. And I dare to advise nobody to advise users to reinstall just for the sport. Thanks for all the help. I not only reinstalled but i also upgraded to 1.0.0B only to find the below : Code: c0000005 (Access violation) Version: 1.0.0B (2007-04-09) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-04-10 23:07:45 TTH: 2HUEVXCV5ML37RZZZVZHTB6D5YSBTQFSOLLIQUA ntdll!0x7C918FEA: RtlpWaitForCriticalSection ntdll!0x7C90104B: RtlEnterCriticalSection The client was workin fine with nothinh else running since i was testing its behaviour. It gave way after 6 hrs when it crashed. The report looks small so i guess i will get a solution soon :D Share this post Link to post Share on other sites
Posted April 10, 2007 GOD help my soul attain APEX as it was before and as it should remain till thy end. . . .Amen Code: c0000005 (Access violation) Version: 1.0.0B (2007-04-09) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-04-11 00:56:16 TTH: QFNOVZRER2VLP2L3L23QNSWT5GUHOA5RBWACN3I ntdll!0x7C918FEA: RtlpWaitForCriticalSection ntdll!0x7C90104B: RtlEnterCriticalSection d:\cvs\apexdc++\trunk\windows\hubframe.h(82): HubFrame::ProcessWindowMessage d:\program files\microsoft visual studio 8\vc\atlmfc\include\atlwin.h(3078): ATL::CWindowImplBaseT<WTL::CMDIWindow=0x02C6C280,ATL::CWinTraits<1456406528=0x00000000,64> >::WindowProc USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E41B89B: GetParent USER32!0x7E41B903: SendMessageW d:\cvs\apexdc++\trunk\windows\mainfrm.h(193): MainFrame::ProcessWindowMessage d:\cvs\apexdc++\includes\wtl\atlframe.h(1623): WTL::CMDIFrameWindowImpl<MainFrame=0x00000000,WTL::CMDIWindow=0x00000111,ATL::CWinTraits<114229248=0x00008007,262400> >::MDIFrameWindowProc USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E41C63F: IsWindowUnicode USER32!0x7E41C665: CallWindowProcW d:\program files\microsoft visual studio 8\vc\atlmfc\include\atlwin.h(3969): ATL::CContainedWindowT<ATL::CWindow=0x0012F198,ATL::CWinTraits<1442840576=0x00000111,0> >::WindowProc USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E41B89B: GetParent USER32!0x7E41B903: SendMessageW COMCTL32!0x7744489A: Ordinal384 COMCTL32!0x7744570B: CreateToolbar USER32!0x7E418734: GetDC USER32!0x7E418816: GetDC USER32!0x7E4189CD: GetWindowLongW USER32!0x7E418A10: DispatchMessageW d:\cvs\apexdc++\includes\wtl\atlapp.h(584): WTL::CMessageLoop::Run d:\cvs\apexdc++\trunk\windows\main.cpp(431): Run 0x001404E8: ? ApexDC!0x0044E2A8: MainFrame::FileListQueue::`scalar deleting destructor' ApexDC!0x00469BAC: [thunk]:MainFrame::`vector deleting destructor' kernel32!0x7C830000: CreateFiberEx 0x90909090: ? Share this post Link to post Share on other sites
Posted April 11, 2007 first off I will apologize for 2 things, first off the numerous issues your having with the new Beta. When your coding a software and adding as many new implementations as has been completed, it is possible to overlook areas. Because the software is being customized, its hard at times to narrow down certain features, that work for most, and crash for others. This is mainly because things can be modified so much. The operating system, tweaks, etc. can all make a difference on how the client runs. the information provided will be helpful in attaining and hopefully resolving the problem. As for TechGeeks, its there mainly because, so many ppl are new to DC and are installing this client for the first time. TechGeeks is the support hub for Apex to help sort out any problems and client issues, before you go off gallivanting around DC. to make your overall DC experience even better. To my knowledge no other client on DC, has a hub dedicated to helping in a similar fashion. HOWEVER, do make note. BEFORE you move any files into your updated client, actually start the client, and put something in for the settings, don't have to be much, just enough to get you going, close and reopen, it should automatically start the TechGeeks hub to help you if needed. IF not, simply close the client and copy your settings into your updated client. this so far has worked every time since the beginning of PWDC. But make sure you get to the hub FIRST. the initial client creates everything needed (xml files) AFTER you fill out the information. so if you update prior to first launch, it WILL auto overwrite. Hope this helps Share this post Link to post Share on other sites
