When zipfs is finalized, be sure to unregister it. If this isn't done,

then path resolution can re-enter the zipfs implementation code and try to
lookup pathnames in hash tables that have been deleted. Crash! Panic! Bad!

I see this easily in an app that embeds Tcl/Tk and uses multiple interps.
Did not easily find a demo script in Tcl alone.

1 files changed, 1 insertions, 0 deletions

diff --git a/generic/tclZipfs.c b/generic/tclZipfs.c
index 82e125c..3b1d787 100644
--- a/generic/tclZipfs.c
+++ b/generic/tclZipfs.c
@@ -5773,6 +5773,7 @@ ZipfsExitHandler(
 
 static void
 ZipfsFinalize(void) {
+    Tcl_FSUnregister(&zipfsFilesystem);
     Tcl_DeleteHashTable(&ZipFS.fileHash);
     ckfree(ZipFS.fallbackEntryEncoding);
     ZipFS.initialized = -1;