hansva opened a new issue, #8972: URL: https://github.com/apache/hop/issues/8972
### Apache Hop version? 2.20.0-SNAPSHOT ### Java version? 21 ### Operating system Windows ### What happened? ## Hop GUI floods the log with "VFS namespace … is closed" and becomes unresponsive after switching projects After switching projects in Hop GUI, the log can fill up with this message: ``` The VFS namespace of Hop GUI <id> is closed. Resolving with the process wide file system manager instead. ``` It repeats for every file that gets resolved, and the linter resolves a lot of them. At debug log level the GUI becomes very slow. ### Cause `HopGui.useVfsNamespaceOfOpenProject()` binds the new project's VFS namespace to the thread and then releases the previous one. When the new project has no namespace of its own (the normal desktop case), `bindThread(null)` leaves the old binding in place. The previous namespace is then closed, but it is still bound to the UI thread. Threads started from the UI thread inherit that binding, the linter's background thread among them. From then on, every file they resolve hits the closed-namespace fallback in `HopVfs.managerOf()` and logs the message. Files still resolve correctly through the process-wide manager. The problem is the log flood and the extra detour on every resolve. ### Fix - `HopGui` clears the thread binding when the new project has no namespace of its own. - In single-tenant mode, a thread that finds its bound namespace closed falls back once and then drops the binding. This covers threads that inherited it before the fix. Hop Web keeps rebuilding the namespace as it does today. ### Issue Priority Priority: 2 ### Issue Component Component: VFS -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
