https://issues.apache.org/bugzilla/show_bug.cgi?id=54162
--- Comment #5 from Massimo Manghi <mxman...@apache.org> --- (In reply to comment #4) > Created attachment 29923 [details] > Delete our own interpreter instead of calling Tcl_Finalize > > Maybe, instead of calling Tcl_Finalize -- which makes it impossible to > libtcl in the process again, rivet should limit itself to deleting just the > interpreter it created? > > Then everyone should be happy... It's probably so, separating the pools wouldn't make any difference because Tcl is not allocating from it and moreover you're corrent in saying that if the child process is exiting where is the point of calling Tcl_Finalize as log as we are using prefork as MPM. Mikhail, please, would you test on your installation if this should work out a solution? After all your set up seems to be the de-facto standard for the reproducibility of the bug. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
