#2454 Multiple bugs in DocFetcher Portable 1.1.25 and 1.1.27 on Windows 11 with 4K display and dual-partition USB drive

[Anonymous]

Subject: Multiple bugs in DocFetcher Portable 1.1.25 and 1.1.27 on Windows 11 with 4K display and dual-partition USB drive
System Configuration:

Windows 11
Display: 3840x2400 resolution at 300% scaling
DocFetcher 1.1.25 and 1.1.27 Portable on Sabrent USB drive
USB drive has two partitions: Partition 1 = Windows 11 bootable partition, Partition 2 = data partition running DocFetcher

Important note on USB drive setup: The USB drive is only connected after booting the PC, so the Windows 11 boot partition on the drive is not involved in the PC's own boot process. However, Windows may still be holding the boot partition open after the drive is connected, preventing the entire physical drive from ejecting even when DocFetcher is properly closed.
Bug 1: Menu bar completely missing on 4K high DPI display
On a 3840x2400 display, the DocFetcher portable window opens with no menu bar visible. The title bar and all panels render correctly, but there is no File/Edit/View menu bar at all. Keyboard shortcuts Alt+F, Alt+V, Alt+H produce no response. This affects both versions 1.1.25 and 1.1.27.
Attempted workarounds with no effect:

Windows display scaling changed from 300% to 150%
Resolution changed to 800x600 and 1280x1024
Window position manually edited in settings-conf.txt
MainShellMaximized = true set in settings-conf.txt
High DPI override set to "Application" in executable compatibility settings

Bug 2: USB drive cannot be ejected after closing DocFetcher
After closing DocFetcher, the USB drive cannot be ejected. This affects both versions 1.1.25 and 1.1.27. Investigation revealed that javaw.exe daemon processes continue running in the background after the main window closes, holding the drive open.
Additional complication: The dual-partition nature of the USB drive may mean Windows is independently holding the first (boot) partition open, preventing ejection of the physical drive regardless of DocFetcher's state. This could not be fully confirmed but is suspected as a contributing factor.
The only reliable way to release the drive found during testing was:

Kill all Java processes via Task Manager or PowerShell
Restart Windows Explorer
Use PowerShell eject command or wait for LED to go off

Bug 3: Stale lock file prevents startup (version 1.1.27 specific)
When DocFetcher 1.1.27 is force-closed or the USB drive is unplugged without properly exiting, a stale lock file is left behind at:
\DocFetcherPortable\indexes.indexes.txt.lock
On next startup DocFetcher reports another instance is already running and refuses to start. The lock file has system+hidden attributes making it invisible in Windows Explorer even with "show hidden files" enabled. Manual deletion via PowerShell is required.
Note: This bug was not observed in version 1.1.25, which closes cleanly via the X button without any configuration changes. Version 1.1.27 required the following config edits to achieve the same clean shutdown:

CheckSingleInstance = false in program-conf.txt
FixWindowSizes = true in program-conf.txt
MainShellMaximized = true in settings-conf.txt

This represents a clear regression between versions 1.1.25 and 1.1.27.
Impact: The combination of these bugs makes DocFetcher portable unusable on a USB drive on high DPI Windows 11 displays:

No menu bar means no File → Exit for clean shutdown
Drive cannot be ejected safely after use
Version 1.1.27 leaves stale lock files requiring manual cleanup every session

Suggested fixes:

Fix Java/SWT menu bar rendering on high DPI Windows 11 displays
Ensure all daemon processes are fully terminated when main window closes
Clean up stale lock file automatically on next startup if no actual instance is running
Add an alternative exit button or keyboard shortcut independent of the menu bar
Investigate dual-partition USB drive ejection behavior

[Anonymous]

During testing of DocFetcher's indexing functionality, 69 PDF files in the Epstein Files Dataset 10 (DOJ Disclosures - Epstein Files Transparency Act HR_4405) were flagged with the error "End-of-File, expected line at offset XXXXX". This turned out to be unrelated to DocFetcher itself — the files were corrupted in the Internet Archive source zip. DocFetcher correctly identified and reported the corrupted files, which is actually a testament to its robust error reporting. The corrupted files were successfully replaced by downloading directly from the DOJ website. No action required on the DocFetcher side.

[Nam-Quang Tran]

Regarding issue #1 ("missing menu bar"): DocFetcher doesn't actually have a traditional File/Edit/View menu bar in the main window. The main window's controls are all in a toolbar (with buttons and dropdowns) plus right-click context menus, and there's a separate popup menu on the system tray icon.

[Nam-Quang Tran]

Issues #2 and #3 (USB drive ejection and stale lock file) will be fixed in DocFetcher 1.1.28.