Adding Close before Remove (possible Windows problem) draft
authorISHIKAWA, Chiaki <>
Sat, 12 Feb 2022 10:52:19 +0900
changeset 113735 4e3e60aeb28a4faec753fb04b6ce10188bea5d08
parent 113734 9c1d3c6e7a5144c2bb8b0e6ba8b120ed84daa2f6
child 113736 ae0aafe8e45a81990b95138cf2728bf772c7a47d
push id15363
push dateSat, 12 Feb 2022 01:52:53 +0000
treeherdertry-comm-central@c99bc5a88b76 [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);