• Enhanced error handling in search index clearing with proper resource management
• Reduced log level for non-critical messages to decrease console noise
• Removed unused imports and properties from GUI state manager
• Improved file deletion robustness with exception handling per file

Remove unused imports and properties

• Removed unused imports: Bindings, BooleanBinding, ObjectProperty, SimpleObjectProperty,
 AutomaticFieldEditorUndoableEdit
• Deleted unused field properties: anyTaskRunning, tasksProgress, lastAutomaticFieldEditorEdit
• Changed log level from info to debug for "No open database detected" message

jabgui/src/main/java/org/jabref/gui/JabRefGuiStateManager.java

Reduce theme manager log verbosity

• Changed log level from info to debug for theme update messages (2 occurrences)
• Reduces console output for non-critical theme change notifications

jabgui/src/main/java/org/jabref/gui/theme/ThemeManager.java

Reduce CSL style loader log level

• Changed log level from info to debug for "Loaded {} CSL styles" message
• Reduces console noise for routine style loading operations

jablib/src/main/java/org/jabref/logic/citationstyle/CSLStyleLoader.java

Description

IndexManager.clearOldSearchIndices now logs an ERROR (with stack trace) for every individual path
that cannot be deleted. Because this cleanup runs during GUI initialization, repeated deletion
failures in an index directory can generate very large logs and slow down startup.

Code

jablib/src/main/java/org/jabref/logic/search/IndexManager.java[R251-259]

+                    try (Stream<Path> indexPath = Files.walk(directory)) {
+                        indexPath.sorted(Comparator.reverseOrder())
+                                 .forEach(file -> {
+                                     try {
+                                         Files.deleteIfExists(file);
+                                     } catch (IOException e) {
+                                         LOGGER.error("Could not delete file {}", file, e);
+                                     }
+                                 });

Evidence

The per-file deletion loop logs at ERROR level inside the forEach, so a directory with many
undeletable files produces one ERROR+throwable per file. This method is invoked during application
initialization, so the impact occurs on every startup when the cleanup runs.

jablib/src/main/java/org/jabref/logic/search/IndexManager.java[233-268]
jabgui/src/main/java/org/jabref/gui/JabRefGUI.java[165-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`IndexManager.clearOldSearchIndices()` logs an `ERROR` (including stack trace) for every single file that fails to delete. When many files fail (e.g., locked/permission issues), this can flood logs and slow startup.

### Issue Context
This cleanup runs during `JabRefGUI.initialize()`, so the logging behavior affects startup performance and log signal-to-noise.

### Fix Focus Areas
- jablib/src/main/java/org/jabref/logic/search/IndexManager.java[251-262]
- jabgui/src/main/java/org/jabref/gui/JabRefGUI.java[185-186]

### Suggested fix approach
- Track failures while iterating (e.g., `AtomicInteger failedDeletes`, store first exception).
- Log **one** summary per directory at `WARN`/`ERROR` (e.g., "Failed to delete N paths under {dir}") and optionally log per-file failures at `DEBUG`.
- Alternatively, use `Files.walkFileTree` with a `FileVisitor` and consolidate failures into a single log message per directory.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools