From 3db9cc3957b3836cc01f6f910a2305bae24318c5 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 20 Mar 2026 14:11:32 +0000 Subject: [PATCH] Fix duplicate memory monitor settings loading on startup Remove redundant LoadMemoryMonitorSettings() call in ApplicationContext.LoadSettings(). The CustomScheduler constructor already loads these settings, so the call in LoadSettings() was causing a third unnecessary load on every startup. The method remains callable from MainForm.RefreshSettings() for when users actually change options. https://claude.ai/code/session_019Awk1AL8nMfrcMU753RxCd --- Class/ApplicationContext.vb | 3 --- 1 file changed, 3 deletions(-) diff --git a/Class/ApplicationContext.vb b/Class/ApplicationContext.vb index c90c5d8..a9eb503 100644 --- a/Class/ApplicationContext.vb +++ b/Class/ApplicationContext.vb @@ -99,9 +99,6 @@ Namespace LiteTask ' Initialize email notification system End If - ' Reload memory monitor and daily restart settings on the scheduler - _customScheduler.LoadMemoryMonitorSettings() - _logger.LogInfo("Settings loaded successfully") Catch ex As Exception _logger.LogError($"Error loading settings: {ex.Message}")