Closed
Bug 286694
Opened 20 years ago
Closed 9 years ago
NS_ASSERTION(NS_SUCCEEDED(rv),"failure cleaning up cache");
Categories
(Core :: Networking: Cache, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: timeless, Unassigned)
Details
(Keywords: assertion)
i have about 3 mfcembeds running, and an ipcd (the ipcd is fairly drunk [in
addition to having caused the first mfcembed to deadlock while quiting], see
other bugs).
+
{,,xpcom_core.dll}((*(nsACString*)(&(*(nsCSubstring*)(&(*(nsLocalFile*){*}item).mWorkingPath))))).mData
0x019c1ec8 "C:\Documents and Settings\____\Application
Data\MfcEmbed\Profiles\default\1wf0fzld.slt\Browser\Cache.Trash\Trash" char *
rv 0x80004005 unsigned int
ntdll.dll!_DbgBreakPoint@0()
xpcom_core.dll!nsDebugImpl::Break(const char * aFile=0x014e6724, int
aLine=0x000003a4) Line 385 C++
xpcom_core.dll!nsDebugImpl::Assertion(const char * aStr=0x014e676c, const char
* aExpr=0x014e6758, const char * aFile=0x014e6724, int aLine=0x000003a4) Line
301 C++
xpcom_core.dll!nsDebug::Assertion(const char * aStr=0x014e676c, const char *
aExpr=0x014e6758, const char * aFile=0x014e6724, int aLine=0x000003a4) Line 109 C++
> necko.dll!DoDeleteFileList(void * arg=0x019bead8) Line 932 + 0x25 C++
nspr4.dll!_PR_NativeRunThread(void * arg=0x019be670) Line 436 + 0xd C
nspr4.dll!pr_root(void * arg=0x019be670) Line 116 + 0xd C
msvcr71d.dll!_threadstartex(void * ptd=0x003f3948) Line 241 + 0xd C
kernel32.dll!_BaseThreadStart@8() + 0x37
Comment 1•20 years ago
|
||
so, you are using ipcd for something? do you have any patches in your tree that could explain this?
Summary: NS_ASSERTION(NS_SUCCEEDED(rv),"failure cleaning up cache"); → NS_ASSERTION(NS_SUCCEEDED(rv),"failure cleaning up cache");
i only have one nontrivial patch to network, it's for the res protocol handler. i don't seem to have any patches to ipc.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P5
Updated•19 years ago
|
Priority: P5 → --
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•