A fix to scheduler code to get around a possible memory leak was causing it to bomb after a number of connections. We have backed out this change for now and the scheduler seems to be working OK at this point.


log in

Advanced search

Message boards : News : A fix to scheduler code to get around a possible memory leak was causing it to bomb after a number of connections. We have backed out this change for now and the scheduler seems to be working OK at this point.

Author Message
SETI News
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Dec 09
Posts: 382
Credit: 0
RAC: 0
Message 956486 - Posted: 29 Aug 2004, 0:00:00 UTC

A fix to scheduler code to get around a possible memory leak
was causing it to bomb after a number of connections.
We have backed out this change for
now and the scheduler seems to be working OK at this point.

Message boards : News : A fix to scheduler code to get around a possible memory leak was causing it to bomb after a number of connections. We have backed out this change for now and the scheduler seems to be working OK at this point.

Copyright © 2014 University of California