(BUG?) XMBC "freezing" for about 3 seconds after running Simulated Keys once.

[jimmyfernandes]

Please fill in this template when posting!

XMBC Version:
XMBC Version: 2.20.5

Installed or Portable version:
Installed

Windows Version:
Windows 11 Pro (64-bit) -Version 24H2

Mouse Information (brand/model):
super basic Multilaser mouse

Relevant Computer Information (CPU, RAM etc):
Intel i3-10100K, 8GB RAM, No Graphics Card

Did the problem occur after an upgrade of XMBC? (If so, from what version?):
No

Did the problem occur after a Windows update/upgrade? (If so, from what version?):
It could be but i'm not sure about it. I Can't tell about what version was either.

How long have you used XMBC?:
About 5 years

What language and keyboard layout do you use in Windows?:
Brazilian Portuguese (PT-br) layout

Clear description of the problem - try and include as much information as possible, including what button and mappings you are having problems with (if applicable).:

There is some kind of bug going on with my Simulated Keys on my Middle Button. After running all the Keys it stops for no reason for about 3 seconds and then it "starts" again. This wierd bug started a few months ago and its been annoying me since then because it takes a lot longer to finish my boring task at my job. I feel like its a Windows thing but i can't prove or test it out.

I have the following simulated Keys: {CTRL}C{WAITMS:230}{TAB}{WAITMS:230}{ALT}{TAB}{WAITMS:200}{CTRL}V{TAB}{WAITMS:200}{ALT}{TAB}{WAITMS:230}{CTRL}C{WAITMS:230}{TAB}{WAITMS:230}{ALT}{TAB}{WAITMS:200}{CTRL}V{TAB}{WAITMS:200}{ALT}{TAB}{WAITMS:230}{CTRL}C{WAITMS:200}{TAB}{WAITMS:230}{ALT}{TAB}{WAITMS:230}{CTRL}V{TAB}{WAITMS:230}{ALT}{TAB}{WAITMS:230}{CTRL}C{WAITMS:230}{ALT}{TAB}{WAITMS:230}{SHIFT}{TAB}{WAITMS:250}{SHIFT}{TAB}{WAITMS:230}{SHIFT}{TAB}{WAITMS:230}{CTRL}V{WAITMS:230}{NUMENTER}{WAITMS:200}{NUMENTER}{WAITMS:200}{NUMENTER}{WAITMS:200}{NUMENTER}{WAITMS:250}{ALT}{TAB}{WAITMS:230}{HOME}{WAITMS:230}{DOWN}{WAITMS:230}

Help please!

[phil]

Do yo mean after it has sent the last key?
How are you sending the keys - what method - is it a repeating sequence?

There are an awful lot of waitms's in there so its going to take time to process that before it can do much else, but if it worked before, I guess its not simply that.

Also, as you are using XMBC 2.20.5, which has been out since June 2023, Im guessing that whatever changed a few months ago, it wasn't XMBC itself.
I don't know if Win11 24H2 works with XMBC (Ive not yet got it to test with) so I guess its possible that something there is dodgy...

I think I'm going to need to see some debug log after its "locked up" for three seconds to see if there are any clues in there, and there's not a lot else to go on. Also it might be useful to have a copy of your profile so I can attempt to reproduce it.

Does it lock up for 3 seconds in simple apps like notepad? or only in specific ones?

[jimmyfernandes]

Good afternoon!!


Yes, It's a repeating sequence, I'm copying the data from a google sheets' sheet and pasting into my job's software. Each cycle is 1 row from the sheet. I need to keep these {WAITMS:} because otherwise it would become a mess, the delay helps with that, all the data is "transported" perfectly.
It's a boring task that I must do every single day. The MXBC saved my life.

I'll try the XMBC previous version to see if it works better.

How can i get this debug log that you mentioned? Is it directly from the XMBC or other app?


Windows Low Level Hook Timeout (Reboot required)
100(ms)
CPU Priority - High

7 Sticky (repeatedly until button is pressed again)
Auto repeat delay 0 (milliseconds)


I think I cannot post any files yet. I'll send my .xmbcs later I guess.

Thanks!!

[phil]

Ive manually edited your profile to remove you from the new users group (that cant post links/files etc). (That normally happens automatically after 4 posts).
Debug logging is enabled in XMBC on the settings -> logging & updates tab.
Enable it, hit OK, hit Apply on the main window.
Reproduce the problem and make a note of the time it happens.
Send me the log and the time it happened (via PM here is best).

Oh and you'd be better off trying the latest Beta to see if it still happens in that (it is much newer - a few weeks now) and close to release, just chasing a few minor issues for a few different users. If its still a problem in that version (2.21 beta 38) it will be much easier for me to investigate as it will be more likely I can reproduce it.

Also when you send the log, it would be good to get a copy of your profile if possible (save profile button), that way I can try and reproduce with a copy of your entire setup.

Regards,
Phil