https://bugs.kde.org/show_bug.cgi?id=501713
--- Comment #1 from zephyrus00jp <ishik...@yk.rim.or.jp> --- You can find the use of SyncRunnable::DispatchToSend() in comm-central thunderbird tree. https://searchfox.org/comm-central/search?q=SyncRunnable%3A%3ADispatchToThread%28&path=&case=false®exp=false Within the code used only by Thunderbird: Textual Occurrences (43 lines across 31 files) mailnews/base/src/nsMsgContentPolicy.cpp 212 mozilla::SyncRunnable::DispatchToThread( <--- modified in 2025 mailnews/base/src/nsNewMailnewsURI.cpp 61 mozilla::SyncRunnable::DispatchToThread( <--- modified in 2023 73 mozilla::SyncRunnable::DispatchToThread( <--- ditto 90 mozilla::SyncRunnable::DispatchToThread( <--- ditto 160 mozilla::SyncRunnable::DispatchToThread( <--- modified in 2019 mailnews/imap/src/nsImapProtocol.cpp 1292 mozilla::SyncRunnable::DispatchToThread( <-- modified in 2023 <--- THIS WHERE THE PROBLEM was reported. 1317 mozilla::SyncRunnable::DispatchToThread( <-- modified in 2023 1345 mozilla::SyncRunnable::DispatchToThread( <--- modified in 2023 The rest of the listing is in mozilla-central which is used by Firefox and thunderbird shares it. In order to learn the modify date of the code, we need to access the M-C tree: https://searchfox.org/mozilla-central/search?q=SyncRunnable%3A%3ADispatchToThread%28&path=&case=false®exp=false Many have been creatd in 2010's and in 2020, etc. and thus if Firefox developers have run firefox under valgrind, they may have reported the issue already. So maybe newer versions of valgrind has issue(s) [maybe it does not handle thread sync related primtives correctly? Maybe hellgrind does and memcheck forgets to handle some primitives?]. Or thunderbird does something wrong which firefox gets right. Just a thought. -- You are receiving this mail because: You are watching all bug changes.
