Strange, I have figures different from Nicolas: -- before ScriptLoader loadOBAlpha -- Socket allInstances size 0 HTTPSocket allInstances size 0 FileStream allInstances size 0 -- after ScriptLoader loadOBAlpha, the debugger is still up -- Socket allInstances size 0 HTTPSocket allInstances size 2 FileStream allInstances size 0 Alexandre On 1 May 2009, at 04:04, John M McIntosh wrote:
Well yes, and the magic check would be
FileStream allSubInstances size inspect
same place as the socket.
Nothing of course finalization is involved in getting rid of zombie file handles too.
And Dave is right you should only have one file handle open (read/ write) for *.changes
On 30-Apr-09, at 4:30 PM, David T. Lewis wrote:
Well that's a bug for sure. Somebody is opening new file streams on the changes file, probably by accident. And not closing the one they opened last time.
The bug in changes file handling could easily appear to be a socket problem, because the per-process limit on open descriptors would be shared between files and sockets (and pipes and ...). So find out why the changes file is being accidentally reopened, and the "socket problem" will probably go away.
Dave
-- = = = = = ====================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http:// www.smalltalkconsulting.com = = = = = ======================================================================
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.