Sign in to follow this  
Followers 0
MiRaGe

Crash: 1.0.0B4

1 post in this topic

And here's my exception info :) ... it froze after about 24-26 hours of successfull running.

and i'd also like to mention that while with beta3 i had similar values like this:

-=[ Memory usage (peak): 43,07 MB (43,07 MB) ]=-

-=[ Virtual memory usage (peak): 37,57 MB (37,57 MB) ]=-

and with this beta4 things have changed a bit .... uses about 2-2.5* with same amount of hubs openned, user numbers, and uploads and 1-2 downloads

... so the same system, almost (we cannot be 100% sure, but should be around) the same environment, but uses much more resourses ... or at least on my computer :)

Code: c0000005 (Access violation)
Version: 1.0.0B4 (2007-08-07)
Major: 5
Minor: 1
Build: 2600
SP: 2
Type: 1
Time: 2007-08-09 11:07:32
TTH: 7CNQCQXDGEV7S2IDTUSYEW73M722LLS7BVOOXDI

ntdll!0x7C918FEA: RtlpWaitForCriticalSection
ntdll!0x7C90104B: RtlEnterCriticalSection
d:\cvs\apexdc++\trunk\windows\hubframe.h(81): HubFrame::ProcessWindowMessage
d:\program files\microsoft visual studio 8\vc\atlmfc\include\atlwin.h(3078): ATL::CWindowImplBaseT<WTL::CMDIWindow=0x03569008,ATL::CWinTraits<1456406528=0x00000000,64> >::WindowProc
USER32!0x7E368734: GetDC
USER32!0x7E368816: GetDC
USER32!0x7E3689CD: GetWindowLongW
USER32!0x7E368A10: DispatchMessageW
d:\cvs\apexdc++\includes\wtl\atlapp.h(992): WTL::CMessageLoop::Run
d:\cvs\apexdc++\trunk\windows\main.cpp(431): Run
0x000705B8: ?
ApexDC!0x0044E0DA: MainFrame::FileListQueue::`scalar deleting destructor'
ApexDC!0x0046A7F1: [thunk]:MainFrame::`vector deleting destructor'
0x8351F8E4: ?

if i remember right, it was currently running minimized, while getting this freeze ... it was running still, as lecnt wrote, but couldn't access it, so closed it :)

i hope it helps

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0