New versions crash

[sutz]

I moved from version 2.20 Beta 8 to the latest versions 2.21 Beta then to 2.20.2. Both get creashed from time to time (eliminated from taskbar tray icons) or getting the cursor hangs. How to get to the older versions?

[phil]

When it crashes, does it produce a crash report (offering to send it to me?) or just dissapear?
Is there anything in the log? Can you send it to me?

You can get old versions using the following URL and just change the number at the end for the version you want....
2.19.2 is 2190200
2.20.0 is 2200000
and so on...
https://www.highrez.co.uk/scripts/downl ... on=2190200

But it would be good to try and find whats going on so I can fix it!

[sutz]

No it doesn't produce a crash report. Suddenly while doing an action with the mouse, the cursor shape gets smaller and moves falteringly (for a while) with the symbol (+) and in this time the app disappear from the taskbar. It remains like this (small cursor with + symbol underneath) untill I relaunch the app again.

** I encountered this message while uploading the log file here
Error
Invalid file extension: XMouseButtonControl.log

** I changed it to .txt

[phil]

OK it looks, from the log that it might be going wrong when resuming from sleep - is that your experience or is it closing randomly?
I wonder if it worth checking the interim versions between 2.20 beta 8 and 2.20 release to see exactly where this started happening, then look at the changes... There weren't many between 2.20 beta 8 and 2.20 release - mostly to do with firefox issues!

2.20 Beta 8: https://www.highrez.co.uk/scripts/downl ... on=2200008
2.20 Beta 9: https://www.highrez.co.uk/scripts/downl ... on=2200009
...
... (it only allow me 5 urls - but you should be able to see the numbers at the end of the links and work out the ones for beta 10,11 & 12!
...
2.20 Beta 13: https://www.highrez.co.uk/scripts/downl ... on=2200013
2.20 Beta 14: https://www.highrez.co.uk/scripts/downl ... on=2200014

[sutz]

it looks, from the log that it might be going wrong when resuming from sleep - is that your experience or is it closing randomly?

No,it doesn't occur upon starting windows from sleeping. I am already used to get windows sleeping instead of shutting it down but the crash doesn' t happen as soon as I wake up windows or even after a while. , besides It happens more than one time in the same session.

I wonder if it worth checking the interim versions between 2.20 beta 8 and 2.20 release to see exactly where this started happening

I will do, but this should take some time. Once I find the version that's not crashing I will inform you.

[phil]

it looks, from the log that it might be going wrong when resuming from sleep - is that your experience or is it closing randomly?

No,it doesn't occur upon starting windows from sleeping. I am already used to get windows sleeping instead of shutting it down but the crash doesn' t happen as soon as I wake up windows or even after a while. , besides It happens more than one time in the same session.

OK The log was only giveing some issues around when it wakes from sleep (thats not uncommon) but I don think there related to the lockups.
That isn't really surprising, as to capture more you need to enable debug logging (but its very verbose and not worth it yet - maybe if we can find a particular version to concentrate on).

I wonder if it worth checking the interim versions between 2.20 beta 8 and 2.20 release to see exactly where this started happening

I will do, but this should take some time. Once I find the version that's not crashing I will inform you.

Thanks!

[sutz]

I have been using v2.20 Beta 14 for 3 three days right now, I didn't face any problem while using it. I recently moved to test v2.21 Beta 1 and I think that's the one in which the malfunction starts. After about half an hour of installing, the mouse moved falteringly (lazily) before (or while) the app crash.
And here is the updated log:

[phil]

That's interesting, so did you try the actual releases (2.20, 2.20.1 and 2.20.2) 2.21 Beta 1 comes after 2.20.2...
But there isn't all that many changes between 2.20 Beta 14 and 2.21 Beta 1 so that's good info!
Hopefully I get a chance to look at the logs and code review to see if Ive missed anything obvious over the weekend (no guarantees though as I do have a bit of a busy day on Saturday!)

[sutz]

2.21 Beta 1 comes after 2.20.2...

The packeges names are too confusing to be honest, I needed to write them on a paper to understand what's going on.
It'd be better if there is a page containing all of them in the right order with direct links.

did you try the actual releases (2.20, 2.20.1 and 2.20.2)

I am trying to download 2.20.2 from https://www.highrez.co.uk/scripts/downl ... on=2200200 but I see "The requested download can not be found on the server." Did I write it wrongly?

[phil]

Apologies, that's my fault.. Release versions (not beta) have a different string..., its just XMouse, not XMouseBeta....

2.20 https://www.highrez.co.uk/scripts/downl ... on=2200000
2.20.1 https://www.highrez.co.uk/scripts/downl ... on=2200100
2.20.2 https://www.highrez.co.uk/scripts/downl ... on=2200200

Regards,
Phil

[sutz]

2.20 Not tested.
2.20.1 Tested, Works normally.
2.20.2 Tested, Malfunctioned [crashes].

[phil]

OK thanks, that helps narrow it down a lot - there wasn't too much changed between .1 and .2... Will try and get a look in this week but I'm away next weekend for Easter and my signing certificate expires in a few days so I may not be able to actually build anything until after Easter!

[phil]

OK I thought there were not many changes, but enough to make it a complex look (and nothing particularly obvious!)
If at all possible, an you run 2.20.2 (or 2.21 beta x) with debug logging enabled, until it crashes (note, debug logging turns itself off next time XMBC is run, so if it does not crash and it restarts (intentionally) you will have to turn debug logging on again!

Then when it does crash, can you send me the log (which should be a lot bigger/more verbose), and ideally a rough time at which the crash occurred?
The only significant logging in the files earlier is around a session lock/unlock but that may just be that without debug logging, there is nothing coming out between that and the crash.

[Dolmatov]

Or the user can enable debugging when the program starts, although this is not recommended.

2023-04-04 19 24 22.png

Edit via Regedit:

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
XMouseButtonControl
C:\Program Files\Highresolution Enterprises\X-Mouse Button Control\XMouseButtonControl.exe /notportable /delay /debug

[phil]

although this is not recommended.

Which is why I didnt suggest that