#Wootility (and some other electron apps) not working - instantly crashing

1 messages · Page 1 of 1 (latest)

bitter sierra
#

Hey there.

W10 laptop, GF 1650 Ti.

The wootility app has stopped working for me... alongside of half electron apps. They just stopped working one day during the past two weeks for no discernible reason; some of them, like Signal or GitHub Desktop, can be run with parameters --in-process-gpu or --disable-gpu-sandbox , but Wootility, sadly, isn't one of those.

Beta branch, regular - neither works for me.

App just crashes (though in Process Explorer 2-3 Wootility processes can still be seen - next to werfault and won't automatically close) on run, doesn't even show a window.

Windows' Event Log doesn't give any more details, it's just

Faulting application name: Wootility.exe, version: 5.2.5.0, time stamp: 0x68d70635
Faulting module name: Wootility.exe, version: 5.2.5.0, time stamp: 0x68d70635
Exception code: 0x80000003
Fault offset: 0x000000000712d4cb
Faulting process ID: 0xc5c
Faulting application start time: 0x01dcc7815ee396c6
Faulting application path: C:\Users\<username>\AppData\Local\Programs\wootility\Wootility.exe
Faulting module path: C:\Users\<username>\AppData\Local\Programs\wootility\Wootility.exe
Report ID: 93bb7243-dae8-4234-ab2d-033eb19decf7
Faulting package full name: 
Faulting package-relative application ID:

What I've tried:

  • installed newest GPU drivers
  • installed older, "stable" GPU drivers (with DDU under safe mode in between installs)
  • repaired .NET 4.8 (unsure if it was actual repair or just message after it finished)
  • installed .NET 10
  • sfc /scannow - nothing to fix
  • DISM /Online /Cleanup-Image /RestoreHealth - nothing to fix
  • checking which DLLs fail from SysInternals' Process Explorer
wheat lanceBOT
# bitter sierra Hey there. W10 laptop, GF 1650 Ti. The wootility app has stopped working for...

Thanks for posting your support request!

Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Support Wizard*
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)

Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting

Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it on hold via the Wooting Hub!

Do you need to...

All of these types of requests need to be made via the Wooting Support Wizard!

oak acorn
#

If browser version works I would just use that tbh

#

As far as electron in general goes, event viewer will most likely have an additional event next to that one with actual logs

#

Or you might be able to find a memory dump file that might have more info

bitter sierra
#

I'm sorry, but the browser version is a workaround, not a solution. It's slow, it uses more resources, I need to choose the keyboard and initialise it every time, I have to load all my profiles by hand, this is just tedious and a huge step backward from the speed, simplicity and usability of the desktop app which I've come to love.

The event log event next to the error indeed had a log attached, but it seems devoid of any clues as well.

Most important fields seem to be:

App: Wootility.exe
Version: 5.2.5.0
Path: C:\Users\<username>\AppData\Local\Programs\wootility\Wootility.exe
Fault module: Wootility.exe
Exception code: 80000003
Exception offset: 000000000712d4cb
OS: Windows 10 19045.7058

How do I go about that memory dump? Any kind of wootility's own logs I could be looking at?

oak acorn
#

all of the downgrades you've described from the web version are not true. Maybe you have a "privacy" browser that prevents the features from working, but there is feature parity in both versions.

#

as for the dump, I'm not sure where windows places them

#

i have a lot in C:\Users\<user>\AppData\Local\CrashDumps but there are other places, too

bitter sierra
#

I managed to create a crashdump (~400MB), but when analysing it in WinDbg (run !analyze -v) there's nothing of substance there either, everything still points to a breakpoint:
FAILURE_BUCKET_ID: BREAKPOINT_80000003_Wootility.exe!Unknown

My browers are compartmentalised and use privacy extensions and it might be the case that those are interfering, but the desktop app used to work beautifully.

oak acorn
#

I'm not sure how we can help you. You mentioned the params to disable hw accel don't work? I guess we could make those work and you would be able to use that option then

#

but it would be a lot slower (I suspect your browser wootility is slow because of this too)

bitter sierra
#

I started testing various chromium parameters seemingly related to GPU and read about --no-sandbox on electronjs reddit and it works with this one!

#

Hopefully other electron apps will work with this param as well.

#

Thanks for the assistance and, please, for the love of everything sacred, do not turn off that flag ;). If you could activate the other flags mentioned it would be cool, too!

oak acorn
#

We didn't explicitly turn on or off any of those flags as far as I'm aware

#

But good that it works for you

bitter sierra
#

Phew, this was stressful. I'm not the one to regularly (or at all) debug someone else's apps, even while being a software tester ;).

plucky steeple
#

kinda weird its needed since the no sandbox flag is mainly needed when the chromiumbased app runs in a virtual machine of some sort.
normally you can check chrome://conflicts to try and figure out what the issue is but thatll be a bit hard in electron apps