If the nodes are small and it worked before, it's probably not size related - I
was thinking of syntax highlighting, but that's probably not it.
Are any of the files you're working with non-local, i.e. on network file
systems? I've had trouble with that, and I think Leo started scanning loaded
files for external changes recently. Seems like that's a possibility.
You can set the threshold for seeing the QT lost data bug (bytes in a single
node), if you don't think the bugs impacting you and you're seeing the warning
too often.
If you're familiar with git, you could try running git bisect to find the exact
commit that broke things.
Re Python and threads, Pyhton's GIL Global Interpreter Lock prevents more than
one *thread* using CPU time at once. But Leo's limited use of threading hasn't
changed recently, that I know of... although on-idle handling did change not
that long ago.
From: Curtis Carlsen <curtiscarl...@gmail.com>
To: leo-editor <leo-editor@googlegroups.com>
Sent: Wednesday, December 14, 2016 1:32 PM
Subject: Re: leo stalling for long periods
The file consists of hundreds of smaller nodes. There may be a few large
nodes, but I find the warning screen about the QT lost data bug annoying so I
usually delete them.
The original file is my work diary, built up over many months. It has lots of
proprietary company data. The boss would not be pleased with me sharing it.
I usually close out the diary files after about a year, because they get slow
to work with. But the symptoms this time are different. Everything is running
along fast and then just stops. It kinda has the feel of a thread getting
stalled by a locked resource. I seem to recall some kind of issue with python
getting locked up on multiprocessors because of a poorly designed global lock,
I have no idea if that could actually be involved, but it's just something I
remember.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
