Hi Edward,

I'm not seeing anything when searching chronologically in the Group here 
for "eventfilter" but its been coming up for me me recently as an issue.

As I read a bit earlier on the group, if you ctrl-c, you get traceback 
data. I did just this, and found that repeatedly pressing ctrl-c lead to 
the issue progressing forward past the initial 'frozen state'.  If you 
want, I could take a screencapture video, it just takes a bit to setup but 
does illustrate the issue a lot better.  Hoping perhaps you've seen it so 
I'm typing a quick note first. 

I launch Leo,  and the following is the backtrace data during multiple 
control-C events. I saw more of the GUI show up, but still the end state 
was a frozen Leo. 
I'll make a video for you a bit later today after I finish some work at the 
datacenter, but in my attempt to install a new Leo on my new laptop vs an 
older one on a much worse laptop (although not much older...just horrid 
lack of enough thermal dissipation causing near constant 200 to 500mhz 
throttling, down from 1800) I came across this problem.

Confirming on my desktop which works peachy with older Leo:

Leo Log Window

Leo 5.4-devel, build 20160722143100, Fri, Jul 22, 2016  2:31:00 PM

Git repo info: branch = master, commit = aca8d416ec35

Python 2.7.10, PyQt version 4.8.7
linux2

setting leoID from os.getenv('USER'): 'mike'

load dir: /home/mike/leo-editor/leo/core

global config dir: /home/mike/leo-editor/leo/config

home dir: /home/mike

reading settings in /home/mike/leo-editor/leo/config/leoSettings.leo

Using default leo file name:
/home/mike/.leo/workbook.leo

reading settings in /home/mike/leo-editor/leo/doc/CheatSheet.leo


But then with the new Git master, it freezes. Same python. 


I'll do a new strace (had older data, and a different scenario of how it 
failed before updating GIT just today, November 10th.. It seemed to fail 
slightly differently about 3 days ago when I first started this message) 


If I do something like: click away the splash screen, move the window to my 
other monitor, and then full-screen resize it from a window, pressing 
ctrl-c a few times in the terminal adjacent to it causes the "frozen" Leo 
to then resize, and somewhat progress in the continuation of its main loop, 
but it keeps getting stuck.


It should be noted, that fullscreen capture of this is considerably 
draining on my CPU on the desktop here, so it was a lot harder to ctrl-c it 
at the right point in its loop to break out and continue with the GUI 
updating. Then after the last time, i hit ctrl-c a few times too many, and 
held it down, and finally Leo caught the interrupt and quit. Without ffmpeg 
going full-out, I was able to trigger the "continuation" within about 3-4 
non-held-down-to-repeat ctrl-c presses. 


Here is the problem in action... https://youtu.be/cAgxr-dO74E - Screen 
recording of the problem in progress. <https://youtu.be/cAgxr-dO74E>


And the output of all that text you see scrolling by... 
https://bpaste.net/show/8fe126429c0f


Please let me know what else you may need.


Thanks,


Mike



-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to