XBMC Freezes (red "X" in icon) after Screen Reawakens

[aoeusnth]

XMBC v2.19.1:
Windows 10 Enterprise:
Evoluent VerticalMouse Left, Kinesis Advantage2 keyboard:
Dell Precision 5530 1080p, 32GB, WD19 USB-C Hub:

Since this might be relevant:

• My USB devices are plugged into the Dell WD19 USB-C hub

• I also connect an external 4K monitor into the WD19 hub

• The Precision 5530 laptop is in clamshell mode (lid shut at all times)

• The laptop is always plugged into the WD19 hub, i.e. it is powered

• I have Win10 set to turn off the (external) display after 20 minutes, but to never allow the laptop to go to sleep

• I have unchecked the "Allow the computer to turn off this device to save power" for the USB 3.1 root hub in the Device Manager

PROBLEM: I've noticed that when "reawakening" the laptop — which means moving the mouse to awaken the external monitor itself, as the laptop is always on — the XBMC icon in the system tray will sometimes have a red X through it, but I can neither left- or right-click on it. I have to kill the process in the Task Manager and restart XBMC to get it to work at all.

[phil]

Yes this is a known problem - XMBC is crashing - and when it crashes it turns on debug (the red bit behind the icon). But because it crashed (well locked up), it does not respond to any clicks.

Did the forum search not work?
https://forums.highrez.co.uk/viewtopic.php?f=6&t=4245
https://forums.highrez.co.uk/viewtopic.php?f=6&t=4243
https://forums.highrez.co.uk/viewtopic.php?f=6&t=4241

I'm working on it - I have a test version which the people who started the above threads are trying for me - its a bit better but not 100% fixed yet. When it is, I will release it!

[aoeusnth]

Oh snap: not only did search "fail" for me, but I didn't realize you had replied to me, either!

In fairness, I didn't actually search for "sleep" or "hibernate", as I wanted to make absolutely clear that my laptop isn't coming out of hibernation — or even sleep — when XBMC locks up.

The laptop is on the whole time, but it has turned off the external monitor. And as far as I know, the Dell WD19 USB-C hub driving both the laptop and all my peripherals is also "alive" the whole time — some evidence of this is when I remote in the resolution is at the 4K of the TV and not the 1080p of the laptop's own display.

Thanks for taking the time to respond, and apologies for the duped ticket.

Some good news today, though: XBMC stayed alive long enough to send a bug report to you.

[phil]

So the resume form sleep/hibernate also applies when simply unlocking - so if the desktop locks, when you unlock it, it runs the same code as when it resumes from sleep - this is new I think in 2.19 and is perhaps the reason for more problems since then. But the good news is that I hope with more reports, its easier to diagnose and fix - and I'm getting there (although annoyingly, I still cant reproduce it on any of my 6 machines - typical!).

You say you sent me a bug report - do you mean from the "crash reported" by email / web reporting or something else?
I've not had any of those for a long time (and I suspect its not working properly but Im not sure why) - Ive certainly not seen any reports come in by email of the website that collects them recently.

[aoeusnth]

You say you sent me a bug report - do you mean from the "crash reported" by email / web reporting or something else?
I've not had any of those for a long time (and I suspect its not working properly but Im not sure why) - Ive certainly not seen any reports come in by email of the website that collects them recently.

Yes, I mean the "crash reported" dialog box. It's the first time I've ever seen XMBC throw it up.

I definitely sent it along, meaning I clicked the button and the dialog box went away (and the system tray icon disappeared when I cursored over it).

[phil]

Well I'm glad it popped up - unfortunately since your last post I have been investigating and it appears the bug report server has not been working for potentially several years {probably since the server was last upgraded)! So I never got it ... I'm working on fixing that (not easy -its 3rd party software and I cant for the life of me figure out whats wrong - looks now to be a "simple" permissions issue but for a simple issue, its being rather tricky to fix - something for tomorrow!

If you do get another one, can you submit it by email (there is an option in the window to send an email) that does work still. I hope that I will get the web server version working of course - and will update in due course.

EDIT: DOH! The bugtrap software I use appears not to work with the server running on HTTPS (secure HTTP) - so since version 2.16 where I switch to using HTTPS everywhere - it has not worked (and I though I have fixed the major crashes LOL ). So I need to either switch back to HTTP only for error/crash reports (not a big deal as its not particularly sensitive) or persuade the BugTrap developers to support HTTPS (and as it hasn't been updated for a couple of years, that may not be possible) or create my own version of it (it is open source at least). I think option A) for the short term at least - unfortunately it means a new build/release of XMBC to change the embedded URL link - so until I release the next version, it will continue to be broken!

[acorderob]

Hi. Maybe i can provide another use case.

Version of the software: 2.19.1 (installed)
Windows Version: Windows 10 Pro x64

I started having this problem when i connected my laptop to my main PC monitor. When i use the laptop i change the input source in my monitor, and thus the connection of the monitor to my main PC is severed as if there was no monitor. Windows does not see the monitor and rearranges opened windows to my second monitor.

When returning the input source to my main PC, after unlocking (it's usually locked because of inactivity), XMBC is freezed. This does not happen when windows just locks up because of inactivity or when the monitor goes to standby, so it must be related to the monitor disappearing (or the move of the hidden window to the other monitor).

[aoeusnth]

EDIT: DOH! The bugtrap software I use appears not to work with the server running on HTTPS (secure HTTP) - so since version 2.16 where I switch to using HTTPS everywhere - it has not worked (and I though I have fixed the major crashes LOL ). So I need to either switch back to HTTP only for error/crash reports (not a big deal as its not particularly sensitive) or persuade the BugTrap developers to support HTTPS (and as it hasn't been updated for a couple of years, that may not be possible) or create my own version of it (it is open source at least). I think option A) for the short term at least - unfortunately it means a new build/release of XMBC to change the embedded URL link - so until I release the next version, it will continue to be broken!

Ah, the life of a developer!

Thanks for chasing it, sorry it hasn't aged well. If you can think of what else we could provide you when XBMC freezes, let us know.

[phil]

Hi. Maybe i can provide another use case.

Version of the software: 2.19.1 (installed)
Windows Version: Windows 10 Pro x64

I started having this problem when i connected my laptop to my main PC monitor. When i use the laptop i change the input source in my monitor, and thus the connection of the monitor to my main PC is severed as if there was no monitor. Windows does not see the monitor and rearranges opened windows to my second monitor.

When returning the input source to my main PC, after unlocking (it's usually locked because of inactivity), XMBC is freezed. This does not happen when windows just locks up because of inactivity or when the monitor goes to standby, so it must be related to the monitor disappearing (or the move of the hidden window to the other monitor).

Thanks for letting me know - as said, I think I'm getting somewhere with this (Ive not had any reports from testers in over a week - so thats promising as they were getting it daily). However, I still haven't been able to reproduce this myself (and recently with video conference meetings on the TV, Ive been plugging/unplugging a lot - but never letting it get locked... So I will try that just to see if I get anything locking up (I better revert to 2.19.1 first I guess!).

I know where its going wrong - when unlocking... Its a thread issue, some sort of resource conflict/timing issue. I still havnt been able to reprocude it once here... and Ive been trying for weeks!. However, I have put lots of logging and protection around it, but I have yet to work out exactly why (well thats not entirely true, I've found lots of possibilities, some significant DOH moments in new 2.19 code and some that have been there for years. The problem with threads and timing, is it will be very much dependant on what else is going on, the CPU speed/usage and all sorts of other possibilities - if it just happens to hit the problem at the wrong time - pop. Anyway its slowly getting better. I hope it wont be long before 2.19.2 - its safe to say its better than 2.19.1 now - maybe I shouldn't be aiming for perfection yet - just a (significant) improvement will be better than nothing - watch this space!

If anyone EVER sees the "crash" window popup, asking you to report the crash (this is rare - it normally does not even show that) then please use the EMAIL button to report to me - that still works - the "report" button tries to send it to my web server, but that fails silently. It will work again in the next version. All good fun!

Regards,
Phil

[mvbentes]

when it crashes it turns on debug

Can I send you some debug or is it too late after it turns it on? I do not get the report dialog.

The forum just lost my last message, so real quick now:

Got to reproduce on win7

1 - Run xmbc
2 - Click here and there (for good measure. Necessary?)
3 - Lock user
4 - Unlock
--- No red x yet
5 - Use button 5
--- red x. If I use button 4 it does not crash and can proceed to use normally.
At this point it does not respond to clicks on the icon. Do not know if I could send anything else to help you diagnose. Close with taskmanager.

Thanks a lot for the amazing work. I am a fan and an ambassador (though a lousy one looking at my converts).



---- TODAY's logs.
*******************************************************************************************************************************************
13-05-2020 09:58:58.352> X-Mouse Button Control v2.19.1 (x64) Startup. Commandline ''
13-05-2020 09:58:58.537> Running in medium integrity mode (0x00002000)
13-05-2020 09:58:58.560> Loaded 23 application specific profiles (15 normal and 8 custom window).
13-05-2020 09:58:58.560> Running on Microsoft Windows 7 Enterprise Edition Service Pack 1 (build 7601), 64-bit, Hook Timeout: 200 ms
13-05-2020 09:58:58.561> Warning: Low Level Hook Timeout is low. If you have problems try increasing this value.
13-05-2020 09:58:58.561> Startup folder: 'C:\Users\user\ArqProg\X-Mouse Button Control\64bit (x64)\XMBCSettings.xml'
13-05-2020 09:58:58.561> Enabling portable mode.
13-05-2020 09:58:58.561> Creating/using settings file in 'C:\Users\user\ArqProg\X-Mouse Button Control\64bit (x64)\XMBCSettings.xml'
13-05-2020 09:58:58.561> As X-Mouse Button Control is not running from an OS protected location (such as 'C:\Program Files\') some features will not work. See the FAQ for more information.
13-05-2020 09:58:58.585> Using keyboard language 0xF0100409
13-05-2020 09:58:58.637> SetHotkeys installed 0 global hotkeys...
13-05-2020 10:00:59.112> You are using the latest available version of X-Mouse Button Control.
13-05-2020 10:09:29.088> CSendInput::ProcessQueue: Failed to send keys. Tried to send 1 keystrokes, sent 0 keystrokes (Error code 5: Acesso negado. )
13-05-2020 10:09:30.719> SPIThread did not exit in a timely fashion!
13-05-2020 10:09:30.862> SetHotkeys installed 0 global hotkeys...
13-05-2020 10:11:19.771> Exit requested by the user.
13-05-2020 10:11:40.072> MultInstance: Sending commandline to an existing instance of X-Mouse Button Control
13-05-2020 10:11:40.074> Received 2048 bytes on the IPC named pipe.
13-05-2020 10:11:40.074> MultInstance: Successfully finished communicating with the first instance of X-Mouse Button Control.

13-05-2020 10:13:00.792> MultInstance: Sending commandline to an existing instance of X-Mouse Button Control
13-05-2020 10:13:00.794> Received 2048 bytes on the IPC named pipe.
13-05-2020 10:13:00.794> MultInstance: Successfully finished communicating with the first instance of X-Mouse Button Control.


*******************************************************************************************************************************************
13-05-2020 10:13:32.313> X-Mouse Button Control v2.19.1 (x64) Startup. Commandline ''
13-05-2020 10:13:32.795> Running in medium integrity mode (0x00002000)
13-05-2020 10:13:32.816> Loaded 23 application specific profiles (15 normal and 8 custom window).
13-05-2020 10:13:32.817> Running on Microsoft Windows 7 Enterprise Edition Service Pack 1 (build 7601), 64-bit, Hook Timeout: 200 ms
13-05-2020 10:13:32.817> Warning: Low Level Hook Timeout is low. If you have problems try increasing this value.
13-05-2020 10:13:32.817> Startup folder: 'C:\Users\user\ArqProg\X-Mouse Button Control\64bit (x64)\XMBCSettings.xml'
13-05-2020 10:13:32.817> Enabling portable mode.
13-05-2020 10:13:32.817> Creating/using settings file in 'C:\Users\user\ArqProg\X-Mouse Button Control\64bit (x64)\XMBCSettings.xml'
13-05-2020 10:13:32.817> As X-Mouse Button Control is not running from an OS protected location (such as 'C:\Program Files\') some features will not work. See the FAQ for more information.
13-05-2020 10:13:32.841> Using keyboard language 0xF0100409
13-05-2020 10:13:32.882> SetHotkeys installed 0 global hotkeys...
13-05-2020 10:14:12.822> CSendInput::ProcessQueue: Failed to send keys. Tried to send 1 keystrokes, sent 0 keystrokes (Error code 5: Acesso negado. )
13-05-2020 10:14:16.937> SPIThread did not exit in a timely fashion!
13-05-2020 10:14:16.971> SetHotkeys installed 0 global hotkeys...

*******************************************************************************************************************************************
13-05-2020 10:15:02.601> X-Mouse Button Control v2.19.1 (x64) Startup. Commandline ''
13-05-2020 10:15:02.633> Running in medium integrity mode (0x00002000)
13-05-2020 10:15:02.652> Loaded 23 application specific profiles (15 normal and 8 custom window).
13-05-2020 10:15:02.653> Running on Microsoft Windows 7 Enterprise Edition Service Pack 1 (build 7601), 64-bit, Hook Timeout: 200 ms
13-05-2020 10:15:02.653> Warning: Low Level Hook Timeout is low. If you have problems try increasing this value.
13-05-2020 10:15:02.653> Startup folder: 'C:\Users\user\ArqProg\X-Mouse Button Control\64bit (x64)\XMBCSettings.xml'
13-05-2020 10:15:02.653> Enabling portable mode.
13-05-2020 10:15:02.653> Creating/using settings file in 'C:\Users\user\ArqProg\X-Mouse Button Control\64bit (x64)\XMBCSettings.xml'
13-05-2020 10:15:02.653> As X-Mouse Button Control is not running from an OS protected location (such as 'C:\Program Files\') some features will not work. See the FAQ for more information.
13-05-2020 10:15:02.678> Using keyboard language 0xF0100409
13-05-2020 10:15:02.733> SetHotkeys installed 0 global hotkeys...
13-05-2020 10:15:32.664> CSendInput::ProcessQueue: Failed to send keys. Tried to send 1 keystrokes, sent 0 keystrokes (Error code 5: Acesso negado. )
13-05-2020 10:15:42.540> SPIThread did not exit in a timely fashion!
13-05-2020 10:15:42.643> SetHotkeys installed 0 global hotkeys...
13-05-2020 10:15:42.802> Using keyboard language 0xF0100409
13-05-2020 10:16:25.444> SPIThread did not exit in a timely fashion!
13-05-2020 10:16:25.504> SetHotkeys installed 0 global hotkeys...

*******************************************************************************************************************************************
13-05-2020 10:17:02.203> X-Mouse Button Control v2.19.1 (x64) Startup. Commandline ''
13-05-2020 10:17:02.253> Running in medium integrity mode (0x00002000)
13-05-2020 10:17:02.274> Loaded 23 application specific profiles (15 normal and 8 custom window).
13-05-2020 10:17:02.275> Running on Microsoft Windows 7 Enterprise Edition Service Pack 1 (build 7601), 64-bit, Hook Timeout: 200 ms
13-05-2020 10:17:02.275> Warning: Low Level Hook Timeout is low. If you have problems try increasing this value.
13-05-2020 10:17:02.275> Startup folder: 'C:\Users\user\ArqProg\X-Mouse Button Control\64bit (x64)\XMBCSettings.xml'
13-05-2020 10:17:02.275> Enabling portable mode.
13-05-2020 10:17:02.275> Creating/using settings file in 'C:\Users\user\ArqProg\X-Mouse Button Control\64bit (x64)\XMBCSettings.xml'
13-05-2020 10:17:02.275> As X-Mouse Button Control is not running from an OS protected location (such as 'C:\Program Files\') some features will not work. See the FAQ for more information.
13-05-2020 10:17:02.302> Using keyboard language 0xF0100409
13-05-2020 10:17:02.341> SetHotkeys installed 0 global hotkeys...

[phil]

I' well on the way to releasing 2.19.2 that should fix this, infact I built it all ready to go this morning. However, Im planning on letting a few people check it before I hit the publish buttons!

Just in case its useful, can I ask a few things...

1. You say it goes wrong when you press button 5 but not button 4 - what are buttons 4 and 5 set to do in XMBC? That may give some useful information?
2. Out of interest, can you reproduce this with debug logging turned on (it will give more info that may help, although quite possibly still not enough as 2.19.1 simply doesn't log the useful stuff (debug or not)).

Some people have been using a test version for about a month now with no issues so I'm fairly confident I've cured it, but its one of those types of bug that makes it difficult to be 100% sure (especially as I have never personally managed to reproduce it; not even once!). If you want to give it a whirl and see if it works for you too, drop me a PM and I'll send you a link to 2.19.2 before I push it out via the release channels.

Thanks,
Phil

[mvbentes]

Hey, Phil!

I could not find a way to put it as an attachment on the forum. I have tried it two more times with debugging on. It seems I was wrong earlier and sometimes it is enough just to lock and unlock the user session.

I have emailed you the debugging log.

Best regards,

MV