You are also running an older version of Ubuntu. Things changed with 16.04. For one, BOINC 7.2.42 won't work in 16.04 unless you jump through hoops and install the needed libraries yourself. I went the other way and compiled the very similar 7.2.47 with static wxWidgets libraries so it would work in 16.04. The first thing We noticed was 7.2.47 wouldn't stop boinc and the running tasks by just exiting the Manager, you had to use Shut down connected Client every time in 16.04, it worked normally in 14.04. That's why I retired 7.2.47 as soon as the Jumping tasks page was fixed and replaced it with 7.4.44 which doesn't have any trouble shutting down boinc and the running tasks. My three Linux machines are all running 7.8.3 and they all shut down the tasks with 10 seconds or less. The problem seems to be the more CPU tasks you're running, the longer it takes to shut down. My machines run at most 2 CPU tasks, and it shuts down very quickly. Those running half a dozen CPU tasks are a different matter with some saying it was taking close to a minute when using the Repository version of BOINC. So, it would appear the time to shut down is related to the number of CPU tasks you are running. You should update one machine to 16.04 so you can see what it's like, it's a bit different than 14.04.

Sorry are you talk to me? Did I Miss something? I'm running Linux Ubuntu 16.04.3 LTS [4.10.0-42-generic]

---

No I believe TBar was replying to Jeff.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Message 1911816 - Posted: 8 Jan 2018, 20:04:16 UTC - in response to Message 1911804.
That one was directed towards Jeff.

I'd say you picked up a few Zombies by stopping and starting BOINC Manager a few times.
Once you clear those, I'd recommend you use Shut Down Connected Client... when stopping and starting BOINC Manager, that will probably cure your problems.

No I believe TBar was replying to Jeff.

OK. Did you see my post? Have any idea why all those task remain in memory?

---

I'm not having any issues on my machines and have no need at present to change my OS. I simply posted my observations to provide more data points to assist in problem resolution. As to number of running CPU tasks, I have one machine running 8, one 7, and one 4. Again, all cleanly terminated within 4 seconds.

You are running an older version of Ubuntu. What works in 14.04 Doesn't work the same as with 16.04, so, your data points are useless to those people in this thread running 16.04.

No I believe TBar was replying to Jeff.

OK. Did you see my post? Have any idea why all those task remain in memory?

No idea. I'd say that you are still running those tasks. I don't know what the refresh poll time is for System Monitor but it can't be more than a 15 seconds or so. If they still are in the process list after a day, I'd say the system still has a process id hanging around. It may be inactive, but it should have been cleaned by now.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

No I believe TBar was replying to Jeff.

OK. Did you see my post? Have any idea why all those task remain in memory?

No idea. I'd say that you are still running those tasks. I don't know what the refresh poll time is for System Monitor but it can't be more than a 15 seconds or so. If they still are in the process list after a day, I'd say the system still has a process id hanging around. It may be inactive, but it should have been cleaned by now.

Last time i run any SSE4.1 app was yesterday before this: Last modified: 7 Jan 2018, 21:36:25 UTC
so at least this 3 was not cleared in the las 24 hrs!
An there are a lot of other AVX2 without clearing just not see for how long but they still there after my post.
They are supposed to be cleared by Boinc? Something is clearly not working as expected on my host.
Maybe that is the real source of the issue.
Anyone of them who write something on the slot lock file will produce the issue.
I leave them for now in the case of anyone wish to test anything.

---

I know you have reloaded BOINC with the tests of version and apps. But have you fully rebooted the system lately? Maybe the linux OS is in a bit of confused state. When was the last time you checked for OS updates via Software Center or Synaptic Package Manager.

I don't have a clue why you have phantom processes running in the System Monitor.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

But have you fully rebooted the system lately?

No. I know if i boot the phantoms will be gone. I will do that latter.
Just living that way in case of any additional test must be suggested

When was the last time you checked for OS updates via Software Center or Synaptic Package Manager.

Yesterday

don't have a clue why you have phantom processes running in the System Monitor.

I'm totally lost too.

I'm at home now so if something lights please let me know.

BTW The host continues to crunch with normal times so that not affect it performance.

---

You are running an older version of Ubuntu. What works in 14.04 Doesn't work the same as with 16.04, so, your data points are useless to those people in this thread running 16.04.

That could only be true if everything in 14.04 worked differently in 16.04, top to bottom. You don't seem to be able to grasp the concept that isolating a problem requires looking at as many different variables as possible until the focus starts to narrow. Right now, that can include OS, BOINC version, application type and version, hardware, task count, etc., etc., and possible combinations of any of those.

So far, we've only recorded observations that the problem occurs with a few applications running under a single BOINC version on very fast hardware. That doesn't really narrow the focus that much. Other observations, and tests run in different environments, may either expand or narrow the scope, by either confirming that the problem exists with different factors in play, or by eliminating certain factors, as long as those tests are repeatable. Simple problem identification and debugging 101. Until specific factors are eliminated, no data points are useless.

I'm totally lost too.

I'm at home now so if something lights please let me know.

BTW The host continues to crunch with normal times so that not affect it performance.

In System Monitor, try right-clicking on each of those processes and choose Properties to see what kind of CPU% and other resources each is consuming. That should tell you if some of them are actually dead or, at least, what's going on with each.

EDIT: Also, the "Open Files" selection in the right-click menu will tell you which files that process has open. Then you can compare each WU file with your active and completed WUs.

You are running an older version of Ubuntu. What works in 14.04 Doesn't work the same as with 16.04, so, your data points are useless to those people in this thread running 16.04.

That could only be true if everything in 14.04 worked differently in 16.04, top to bottom. You don't seem to be able to grasp the concept that isolating a problem requires looking at as many different variables as possible until the focus starts to narrow. Right now, that can include OS, BOINC version, application type and version, hardware, task count, etc., etc., and possible combinations of any of those.

So far, we've only recorded observations that the problem occurs with a few applications running under a single BOINC version on very fast hardware. That doesn't really narrow the focus that much. Other observations, and tests run in different environments, may either expand or narrow the scope, by either confirming that the problem exists with different factors in play, or by eliminating certain factors, as long as those tests are repeatable. Simple problem identification and debugging 101. Until specific factors are eliminated, no data points are useless.

I'll say it again. BOINC is Much different in Ubuntu 16.04 than it is in 14.04. Your comparisons using 14.04 are not helpful at all., and only adds confusion to the thread.
If you want to make other contributions that is fine, but understand that any comparison to the way BOINC 7.2.42 works in 14.04 is Not helpful to those running 16.04.
I have actually compiled different BOINC versions and run them in both systems, if you want to give advice to someone running 16.04 then I suggest you install it so you will have a frame of reference.

I'll say it again. BOINC is Much different in Ubuntu 16.04 than it is in 14.04. Your comparisons using 14.04 are not helpful at all., and only adds confusion to the thread.
If you want to make other contributions that is fine, but understand that any comparison to the way BOINC 7.2.42 works in 14.04 is Not helpful to those running 16.04.
I have actually compiled different BOINC versions and run them in both systems, if you want to give advise to someone running 16.04 then I suggest you install it so you will have a frame of reference.

A new frame of reference only helps if you are prepared to go the extra mile and trace the changes back to source, to establish cause and effect.

If you can prove that the problem only exists in a specific OS version, then post your evidence. Otherwise, put a sock in it. We aren't just trying to help users running 16.04, we are trying to identify the conditions under which the problem may exist. Having the first two reports of the problem occur in 16.04 does not automatically prove that 16.04 is the only OS version in which it might live.

@Jeff

I made what you ask. Post 4 examples on the link. All AVX2 shows all parameters equal as the posted. Each SSE4.1 shows different CPU time. In all the status is Sleep. So they are not phantoms they are sleeping grinch!. Sometimes i really hate computers!

What i can't understand why they still in the memory some after 24 hrs.

https://1drv.ms/u/s!Asjkc9Jyluh3zxFNnAHQAuFT-19J

<edit> One question... What program is supposed to delete the process? Or at least tell the OS to kill the process?

---

A BOINC application in memory can sleep for as long as it likes. But it should keep just enough awareness to listen for further instructions, whether they be 'wake up and crunch', or 'exit completely, we're quitting'.

Ask any Linux developer, there are Major differences between 14.04 and 16.04. The one major difference is the one I've already mentioned and pertains to the problems in this thread. BOINC doesn't always stop the running tasks by just exiting the Manager. That should be pretty clear by now. It was discovered early by trying to run a 7.2.x version. Ask Keith about it, he experienced it first hand with 7.2.47. The solution has already been posted. For those having trouble with the tasks not stopping by exiting the Manager, choose the Shut down connected client... first before exiting the Manager. That was discovered months ago. Now if someone wants to try to get the people at BOINC to do something about it, go for it.

That problem doesn't exist in Ubuntu 14.04, try it yourself.
The problem with the Activity Menu Not working in 16.04 Doesn't happen in 14.04, and appears to be fixed in Ubuntu 17.10. Try it yourself.

Juan, your OneDrive URL link is malformed. Can't get where you intended.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)