Ticket to capture potential resource leak.

[Agent-Hellboy]

Once a stable unit test is in place that covers the key code paths, run the following sanitizers and tools to ensure correctness and robustness:

• AddressSanitizer (ASan)
• UndefinedBehaviorSanitizer (UBSan)
• LeakSanitizer (LSan) (already part of ASan)
• ThreadSanitizer (TSan)
• Static Analysis Tools

[coderabbitai]

Resource leak in test_db_clipboard.cpp

Found during review of PR #24: #24 (comment)

Issue: In the test_get_clipboard() function, the X11 display opened by XOpenDisplay() is only closed on successful execution, risking resource leaks if an exception occurs.

Location: test/test_db_clipboard.cpp lines 33-40

Details: The current code closes the display handle only when the function completes successfully. If an exception is thrown by get_clipboard(), the display resource may leak.

Suggested Fix: Ensure that XCloseDisplay() is called regardless of success or failure by using proper exception handling or RAII pattern.

Reported by: @Agent-Hellboy