Adding Close before Remove (possible Windows problem) draft
authorISHIKAWA, Chiaki <>
Mon, 23 May 2022 03:03:51 +0900
changeset 116832 9b51773175d639290d81cccd461db8005eebf9ff
parent 116831 89c39ab9a6e9f5dc0e6bd34615da3a18c6f8bfa0
child 116833 be5b008ddbee8ff74196284f43d8476bcc323016
push id15955
push dateSun, 22 May 2022 18:04:18 +0000
treeherdertry-comm-central@beaacca97fbd [default view] [failures only]
Adding Close before Remove (possible Windows problem)
--- a/mailnews/local/src/nsPop3Sink.cpp
+++ b/mailnews/local/src/nsPop3Sink.cpp
@@ -267,17 +267,17 @@ nsresult nsPop3Sink::EndMailDelivery(nsI
   // Shouldn't we release it after filter plugins are run below?
   MOZ_LOG(POP3LOGMODULE, mozilla::LogLevel::Debug,
           (POP3LOG("Calling ReleaseFolderLock from EndMailDelivery")));
   nsresult rv = ReleaseFolderLock();
   NS_ASSERTION(NS_SUCCEEDED(rv), "folder lock not released successfully");
   bool filtersRun;
-                              &filtersRun);  // ??? do we need msgWindow?
+                              &filtersRun);  // XXX ??? do we need msgWindow?
   int32_t numNewMessagesInFolder;
   // if filters have marked msgs read or deleted, the num new messages count
   // will go negative by the number of messages marked read or deleted,
   // so if we add that number to the number of msgs downloaded, that will give
   // us the number of actual new messages.
   m_folder->GetNumNewMessages(false, &numNewMessagesInFolder);
   m_numNewMessages -= (m_numNewMessagesInFolder - numNewMessagesInFolder);