Quick update about the subject topic:
I applied the suggested hack immediately on November 20, and got the
associated No file monitor support - changes will go undetected at zim
start.
After some 25 days running with no file monitoring zim is reported to
use 261 threads. While the number
You can hack zim to stop listening for filesystem signals. If that makes
the problem go away, you can at least confirm the root cause.
To do so edit zim/fs.py -- this will be e.g. in /usr/lib/python/zim -
depends on your install locations.
In this file near the top there is a section:
Jaap thank you for taking the time to look into this.
I also have the feeling that this has to do with filesystem's change
notifications.
While zim became a very important part of my everyday's actvity, there
are days worse than others, and today is one of these: I have been
editing files
Hi Jaap,
just a quick update: After recycling zim-wiki the number of threads
stayed in the 11 ballpark for quite a long time. It suddenly started
climbing while I was running a completely unrelated ftp file transfer.
Stopped climbing when the ftp ended, restarted climbing when I
Hello,
I run zim-wiki 0.62 on RedHat Linux 6.5. Happily.
Lately my system started experiencing strange fork failed - resource
temporarily unavailable problems that I see as unrelated to zim-wiki.
Still, trying to diagnose these, I noticed that running a single
instance of zim-wiki
Hi Mario,
I would not consider that to be normal. But to be honest I also never did a
real benchmark on this.
Zim uses threads mostly to make IO a bit more responsive, but those should
threads should be short lived and you would not see many of them in
parallel.
One thing to try is to also
Jaap,
thanks for your kind reply.
To just get the number of active threads issue the following command:
ps -eT|grep zim|wc -l
For a detailed list use: ps -fT -C zim
By the way: After a quit/start and couple of page views zim-wiki sits at
11 threads. I will keep it under control.
7 matches
Mail list logo
