I can repeat my problem on linux, don't know if at all the same as Max users.
It happens while doing:
Installer wiresong
project: 'ob';
install: 'OB-Refactory'.
Once the load is finished:
FileStream allSubInstances size -> 454
ls -l /proc/9091/fd | grep changes | wc -l -> 570
A little mismatch here...
Note that it reached 1018 during load, for a total of 1024 opened fd,
the upper limit...
ls -l /proc/9091/fd | grep -v total | wc -l -> 1024
I can remove in image file stream:
Smalltalk collectGarbage.
FileStream allSubInstances size -> 4
But the file descriptors are not closed:
ls -l /proc/9091/fd | grep changes | wc -l -> 570
Argh!
After a garbage collect, I can proceed loading:
Installer lukas
project: 'omnibrowser';
install: 'OB-Regex';
install: 'OB-Tools'
But dragging these 570 opened change log is not very sane...
Gonna inquire if I can install a strace on my box.
Nicolas
2009/5/1 John M McIntosh <[email protected]>:
> 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 <[email protected]> Twitter:
> squeaker68882
> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
> =
> =
> =
> ========================================================================
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
