Show Posts
1
Support and Feedback / No crash/hang, but after a while no keyboard keystroke is working
« on: May 18, 2017, 19:56:49 »
Hi :-)
I'm using the latest x64 version (install-package) v7.1.2347 and I notice weird, for me not instantly explicable behavior.
My settings are out-of-the-box plain vanilla, with NC-styled shortcuts for function-keys etc. I have not changed a usersettings yet, besides turning on all logfiles.
Using MC extensively for a random amount of time (had it work perfect for 12hrs+ - had it happen after 3m), at some point MC stops reacting to any key press / function key or combination which should invoke the standard commands. MC is NOT crashed or unresponsive !! Working with the mouse clicking the commands or in panels or menu's, does what one expects. But not when controlled / initiated by keyboard.. not in explorer panels or menu or whatever.. EXCEPT.. when I put the focus on the command line bar by clicking it.. and I type text... flawlessly the typed text appears. In all other programs I try on this Win10Pro (x64) machine, the keyboard works with not hitches or unexpected behaviour whatsoever.
I turned on all logfiles (all type informational - switching to debug logging), but searching thru the 42MB of log files of my filemanagement work over the past 3 days, nothing really strikes me as abnormal. No errors reported either.
Two lines I'm not exactly sure what is meant with :
In MultiCommander logs I sometimes see (other times its way less messages of type id f140-0) :
2017-05-17 14:26:37.845 System broadcast message received : id : f140 - 0
+ 233 x same id f140 - 0 message + between the start time above and the time of next line
2017-05-17 14:30:31.845 System broadcast message received : id : f140 - 0
2017-05-17 14:30:32.845 System broadcast message received : id : f170 - 2
2017-05-17 14:30:32.847 System broadcast message received : id : f140 - 0
2017-05-17 14:30:37.844 System broadcast message received : id : f170 - 2
Highly doubted that these messages are connected to what I experience.. because that was NOT one of the times the keys stopped being responsive.. the time it happened after that time yesterday was around 20.00 at night.. several hours later : I would like to know what these id's mean if possible tho :-)
All the management work are the basics : edit, rename, but mainly, F5, F6, F8, tab. Work split over up til 6 tabs left and 6 tabs right (MAXIMUM).
I have more than 12GB RAM free and no issues in speed or responsiveness : not local drives, not networked drives.
My keyboard is not the most standard one (Logitech G19 with Color LCD and 12 Macro Function keys extra), but I've been using this keyboard for years and years and (altho the gaming software is bloated), the Logitech driver for the keyboard itself is proven to be really stable over lotsa years. Since keyboard exactly works like it should in other programs etc, I'm not expecting it to be the keyboard, but will not rule it out completely either.
I will set all logging to maximum level for coming test-periode and see if I can find out more.
Would making a process-dump be useful the moment it stops responding to key-commands, but still being able to type in the command bar ?
I really REALLY want to keep using MenuCommander, since for me it's the one that gives me the best NC-in-DOS-days-feel, combined with exactly the info I want on screen.. and I've tried pretty much all clones/competitors. But it's completely depending on being able to use it with the keyboard only as key usage component of course since that's the true power, besides working with 2 panels and multiple tabs in them each.
Anyone any idea where to look for the solution to this "problem" ? Any insights are appreciated :-)
* turned out to be a long story, but I wanted to describe it as clear and complete as possible, since searching the forums didn't turn up this behaviour yet.. I'm sorry for the long read *
I'm using the latest x64 version (install-package) v7.1.2347 and I notice weird, for me not instantly explicable behavior.
My settings are out-of-the-box plain vanilla, with NC-styled shortcuts for function-keys etc. I have not changed a usersettings yet, besides turning on all logfiles.
Using MC extensively for a random amount of time (had it work perfect for 12hrs+ - had it happen after 3m), at some point MC stops reacting to any key press / function key or combination which should invoke the standard commands. MC is NOT crashed or unresponsive !! Working with the mouse clicking the commands or in panels or menu's, does what one expects. But not when controlled / initiated by keyboard.. not in explorer panels or menu or whatever.. EXCEPT.. when I put the focus on the command line bar by clicking it.. and I type text... flawlessly the typed text appears. In all other programs I try on this Win10Pro (x64) machine, the keyboard works with not hitches or unexpected behaviour whatsoever.
I turned on all logfiles (all type informational - switching to debug logging), but searching thru the 42MB of log files of my filemanagement work over the past 3 days, nothing really strikes me as abnormal. No errors reported either.
Two lines I'm not exactly sure what is meant with :
In MultiCommander logs I sometimes see (other times its way less messages of type id f140-0) :
2017-05-17 14:26:37.845 System broadcast message received : id : f140 - 0
+ 233 x same id f140 - 0 message + between the start time above and the time of next line
2017-05-17 14:30:31.845 System broadcast message received : id : f140 - 0
2017-05-17 14:30:32.845 System broadcast message received : id : f170 - 2
2017-05-17 14:30:32.847 System broadcast message received : id : f140 - 0
2017-05-17 14:30:37.844 System broadcast message received : id : f170 - 2
Highly doubted that these messages are connected to what I experience.. because that was NOT one of the times the keys stopped being responsive.. the time it happened after that time yesterday was around 20.00 at night.. several hours later : I would like to know what these id's mean if possible tho :-)
All the management work are the basics : edit, rename, but mainly, F5, F6, F8, tab. Work split over up til 6 tabs left and 6 tabs right (MAXIMUM).
I have more than 12GB RAM free and no issues in speed or responsiveness : not local drives, not networked drives.
My keyboard is not the most standard one (Logitech G19 with Color LCD and 12 Macro Function keys extra), but I've been using this keyboard for years and years and (altho the gaming software is bloated), the Logitech driver for the keyboard itself is proven to be really stable over lotsa years. Since keyboard exactly works like it should in other programs etc, I'm not expecting it to be the keyboard, but will not rule it out completely either.
I will set all logging to maximum level for coming test-periode and see if I can find out more.
Would making a process-dump be useful the moment it stops responding to key-commands, but still being able to type in the command bar ?
I really REALLY want to keep using MenuCommander, since for me it's the one that gives me the best NC-in-DOS-days-feel, combined with exactly the info I want on screen.. and I've tried pretty much all clones/competitors. But it's completely depending on being able to use it with the keyboard only as key usage component of course since that's the true power, besides working with 2 panels and multiple tabs in them each.
Anyone any idea where to look for the solution to this "problem" ? Any insights are appreciated :-)
* turned out to be a long story, but I wanted to describe it as clear and complete as possible, since searching the forums didn't turn up this behaviour yet.. I'm sorry for the long read *