The FCGI scheduler handles 20 requests, then exits.
On 1/3/2017 8:22 AM, Christian Beer wrote:
The scheduler can also be used as an fcgi executable in which case it
runs indefinitely like the file_upload_handler which would expose the
memory leak.
Regards
Christian
On 03.01.2017 17:18, David Anderson wrote:
It's OK in this case because it's in the scheduler, which runs a
limited number of times then exits.
It's not OK in the client.
On 1/3/2017 7:34 AM, Christian Beer wrote:
As for memory leaks occurring in BOINC I'd like to quote
sched/sched_version.cpp line 515:
// This is a memory leak, but that's OK
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
