@bobfrankston/rmfmail 1.2.274 → 1.2.276

package/client/app.js

@@ -159,6 +159,9 @@ window.__btick && window.__btick("app.ts module body executing");
 let baseTitle = APP_NAME;
 let lastSeenCount = 0;
 let badgeCount = 0;
+/** Last count pushed to the Windows taskbar overlay, so an unchanged count
+ *  is not re-pushed. -1 = nothing pushed yet. See updateBadge. */
+let lastOverlayCount = -1;
 function updateBadge(count) {
     badgeCount = count;
     // Update title
@@ -212,7 +215,19 @@ function updateBadge(count) {
         // taskbar for the whole life of this feature (Bob 2026-05-28 "are you
         // able to show the number of new messages").
         const hostApi = window.mailxapi;
-        if (hostApi?.setTaskbarOverlay) {
+        // Push ONLY when the number actually changes. Windows keeps the
+        // overlay icon alive until the next SetOverlayIcon, so the host
+        // cannot free the icon it just handed over — each push costs the
+        // host process one HICON plus the two bitmaps inside it, and the
+        // unread-count refresh fires every few seconds. That reached the
+        // 10,000-object per-process GDI cap in about a day, after which the
+        // host logged "CreateIconIndirect failed: Not enough memory
+        // resources" on every tick and could create no further GDI objects
+        // (Bob 2026-08-23, measured: rmfmail.exe at GDI=9995). msger now
+        // frees the PREVIOUS icon so the leak is bounded either way; this
+        // just stops the pointless churn (Claude Code 2026-08-23).
+        if (hostApi?.setTaskbarOverlay && count !== lastOverlayCount) {
+            lastOverlayCount = count;
             if (count > 0) {
                 // BADGE-ONLY overlay. SetOverlayIcon composites the supplied
                 // icon onto the bottom-right corner of the taskbar button —