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.

To post messages, you must log in.

AuthorMessage
SETI News
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 16 Dec 09
Posts: 386
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.
ID: 956486 · Report as offensive

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.


 
©2017 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.