Comment 34 for bug 968021

Now running 7.0.34, it does not seem to leak on file descriptor so far (already 10 tasks done).
A collision on disk full (well, allocated space) is probably another issue (best tracked in its own bugreport ?)

7.0.33 was fine too.

My check is :
 $ sudo lsof -p `pidof boinc`

The last file descriptor does not increase as tasks are done (it can raise a bit to send back the result, but later it returns to something always low (like 20 or 30))

As an illustration:

boinc 8538 boinc 0u CHR 1,3 0t0 1029 /dev/null
boinc 8538 boinc 1w REG 8,118 1967980 23 /var/lib/boinc-client/stdoutdae.txt
boinc 8538 boinc 2w REG 8,118 19666 22 /var/lib/boinc-client/stderrdae.txt
boinc 8538 boinc 3wW REG 8,118 0 19 /var/lib/boinc-client/lockfile
boinc 8538 boinc 4w REG 8,118 176550 24 /var/lib/boinc-client/time_stats_log
boinc 8538 boinc 5u CHR 195,255 0t0 38091 /dev/nvidiactl
boinc 8538 boinc 6u CHR 195,0 0t0 38092 /dev/nvidia0
boinc 8538 boinc 7u CHR 195,0 0t0 38092 /dev/nvidia0
boinc 8538 boinc 8u CHR 195,0 0t0 38092 /dev/nvidia0
boinc 8538 boinc 9u IPv4 95350 0t0 TCP *:31416 (LISTEN)
boinc 8538 boinc 10u IPv4 92260 0t0 TCP localhost:31416->localhost:59555 (ESTABLISHED)
boinc 8538 boinc 11u CHR 195,255 0t0 38091 /dev/nvidiactl
boinc 8538 boinc 12u CHR 195,0 0t0 38092 /dev/nvidia0
boinc 8538 boinc 13u CHR 195,0 0t0 38092 /dev/nvidia0
boinc 8538 boinc 14u CHR 195,0 0t0 38092 /dev/nvidia0
boinc 8538 boinc 15r REG 0,15 4224 36018 /run/utmp
boinc 8538 boinc 17u IPv4 89730 0t0 TCP krynn.local:60990->pd2.cs.nctu.edu.tw:http (CLOSE_WAIT)
boinc 8538 boinc 19r REG 0,3 0 4026532036 /proc/interrupts
boinc 8538 boinc 20u IPv4 91746 0t0 TCP krynn.local:60993->pd2.cs.nctu.edu.tw:http (CLOSE_WAIT)