Bugzilla

Found another maybe useful logging facility: MOZ_LOG=MsgDB:5 which is only used in mailnews/db/msgdb/src/nsMsgDatabase.cpp. And that's where summary files (.msf) get "blown away" if there's a problem with the .msf file.  ```summaryFile->remove()``` does the deletion (called in 2 places but so far I've only seen the first one occur).
However,  with MsgDB:5 set, I see no .msf deletions after a long time. Without it set and just IMAP:5 set, the error occurs after about 4 or 5 minutes usually (according to printf's I added to the tb code).
So kind of looking like the problem is somehow timing related. With MOZ_LOG=MsgDB:5,timestamp,sync set, windows is acting like what I see on linux, so far.
See https://searchfox.org/comm-central/rev/20d0dc6c8e767c9059ce80ac154b7df81a8f120e/mailnews/db/msgdb/src/nsMsgDatabase.cpp#1216

**Update** -- failed again after a longer time. Adding more printf's to debug.
Found another maybe useful logging facility: MOZ_LOG=MsgDB:5 which is only used in mailnews/db/msgdb/src/nsMsgDatabase.cpp. And that's where summary files (.msf) get "blown away" if there's a problem with the .msf file.  ```summaryFile->remove()``` does the deletion (called in 2 places but so far I've only seen the first one occur).
However,  with MsgDB:5 set, I see no .msf deletions after a long time. Without it set and just IMAP:5 set, the error occurs after about 4 or 5 minutes usually (according to printf's I added to the tb code).
So kind of looking like the problem is somehow timing related. With MOZ_LOG=MsgDB:5,timestamp,sync set, windows is acting like what I see on linux, so far.
See https://searchfox.org/comm-central/rev/20d0dc6c8e767c9059ce80ac154b7df81a8f120e/mailnews/db/msgdb/src/nsMsgDatabase.cpp#1216