Closed
Bug 85280
Opened 24 years ago
Closed 17 years ago
pop biff urls causing thread safety assertions
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
Future
People
(Reporter: sspitzer, Unassigned)
References
Details
I'm asserting when ever pop biff goes off.
the url that is being run is pop3://sspitzer@mail.meer.net/check
NTDLL! 77f9f9df()
nsDebug::Assertion(const char * 0x02fea304, const char * 0x100e227c, const char
* 0x100e2250, int 528) line 290 + 13 bytes
NS_CheckThreadSafe(void * 0x00482b40, const char * 0x02fea304) line 528 + 34
bytes
nsPop3Sink::Release(nsPop3Sink * const 0x045c6a20) line 38 + 58 bytes
nsCOMPtr<nsIPop3Sink>::~nsCOMPtr<nsIPop3Sink>() line 490
nsPop3URL::~nsPop3URL() line 40 + 11 bytes
nsPop3URL::`scalar deleting destructor'() + 15 bytes
nsMsgMailNewsUrl::Release(nsMsgMailNewsUrl * const 0x045c68e4) line 66 + 132
bytes
nsPop3URL::Release(nsPop3URL * const 0x045c68e0) line 42 + 16 bytes
nsCOMPtr<nsISupports>::~nsCOMPtr<nsISupports>() line 757
nsSocketRequest::~nsSocketRequest() line 2456 + 11 bytes
nsSocketReadRequest::~nsSocketReadRequest() line 2603 + 19 bytes
nsSocketReadRequest::`scalar deleting destructor'(unsigned int 1) + 15 bytes
nsSocketRequest::Release(nsSocketRequest * const 0x045c70f0) line 2440 + 132
bytes
nsSocketTransport::CompleteAsyncRead() line 545 + 24 bytes
nsSocketTransport::doReadWrite(short 0) line 983
nsSocketTransport::Process(short 0) line 477 + 13 bytes
nsSocketTransportService::ProcessWorkQ() line 243 + 10 bytes
nsSocketTransportService::Run(nsSocketTransportService * const 0x014867f4) line
446 + 11 bytes
nsThread::Main(void * 0x01486250) line 105 + 26 bytes
_PR_NativeRunThread(void * 0x01486030) line 399 + 13 bytes
_threadstartex(void * 0x01487e70) line 212 + 13 bytes
KERNEL32! 77e92ca8()
Comment 1•24 years ago
|
||
sounds like a thread proxy is needed, but what interface is nsPop3Sink
implementing here?
Comment 2•24 years ago
|
||
pop3 urls doesn't implement the thread safety addref release macros....this is a
trival fix. but probably won't make the PDT cut.
Target Milestone: --- → Future
Comment 3•24 years ago
|
||
ignore my comment. it's incorrect.
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Assignee: mscott → nobody
QA Contact: esther → backend
Comment 5•17 years ago
|
||
I haven't seen this, ever.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•