[bug] Changing auto DST setting crashes Glasswire UI

Change your TZ to Australia, which just went into DST.
Start Glasswire. Toggle the DST setting on and off
Crash.

Faulting application name: GlassWire.exe, version: 1.1.26.0, time stamp: 0x56025a8e
Faulting module name: Qt5Gui.dll, version: 5.5.0.0, time stamp: 0x55911d00
Exception code: 0xc0000005
Fault offset: 0x0000652d
Faulting process id: 0x183c
Faulting application start time: 0x01d0fdefb14a2595
Faulting application path: C:\Program Files (x86)\GlassWire\GlassWire.exe
Faulting module path: C:\Program Files (x86)\GlassWire\Qt5Gui.dll
Report Id: c55fae3b-e838-435e-bbd0-c274ed856396
Faulting package full name: 
Faulting package-relative application ID:

For some reason we could not reproduce this on our computers, but we’ll keep trying so we can fix it.

I hate to bump this thread, but I am having a similar issue. I installed Glasswire (free version) the other day on my server, which is running Windows 2012 R2. It seems to be great except that it crashes at midnight every night, and loses all the recorded data for the previous day. I came to this thread as I searched for the Qt5Gui.dll error, as in event viewer I get a similar report

Faulting application name: GlassWire.exe, version: 1.1.36.0, time stamp: 0x565fda70
Faulting module name: Qt5Gui.dll, version: 5.5.0.0, time stamp: 0x55911d00
Exception code: 0xc0000005
Fault offset: 0x00006504
Faulting process id: 0xa14
Faulting application start time: 0x01d13d3ef601e808
Faulting application path: C:\Program Files (x86)\GlassWire\GlassWire.exe
Faulting module path: C:\Program Files (x86)\GlassWire\Qt5Gui.dll
Report Id: 32e0f118-a9fb-11e5-80db-848f69f8f635
Faulting package full name:
Faulting package-relative application ID:

I’ll have to see if playing with timezones makes it crash, but given that mine crashes at midnight I do believe the issue is related.

We just released an update this morning, please upgrade and let us know if that fixes it.

Thank you, I just updated it to .39b, I’ll know the result one way or another tonight :slight_smile:

1 Like

I’m sorry for not replying back sooner, I’ve been playing around with this over the holidays. To make a long story short, it still crashes at midnight, but only if the program has the window open. If it is running but in the system tray, it does not crash, it continues to work like normal, and I can open it from the tray and view all the stats like normal.

If the window is open come midnight, it will crash. I was able to get the program to run for a week straight without issue by keeping it only running in the system tray when I’m not actively looking at it.

I hope that helps, if you can think of anything that might help, let me know.

after reading your description Froggy, I think the crash I’m experiencing is this one, actually. I’ll keep GlassWire minimized at midnight tomorrow and see what happens. The window WAS open when it crashed at midnight tonight.

@mattgphoto Please let me know if it happens for you again. I’ll run this by our dev team again and see if they have some ideas.

@Ken_GlassWire looks like it didn’t crash with the app minimized. Shall I keep the window open at midnight tomorrow to see if it crashes again?

Please do so, thanks!

@Ken_GlassWire sorry for the delay, but yes, with the window open, the app crashes at midnight.

We tested carefully with all our machines and we cannot reproduce this but we’ll keep trying.

I’d been away traveling, but I got back to my home pc and kept it open again at midnight, and this still happens for me. If there’s any kind of logs I can provide, let me know.

I will ask the dev team if there is something we can get from you. Thanks for following up on this problem.

Please do the following:

  1. Run regedit.exe
  2. Open key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps
  3. Add a new key “GlassWire.exe” under the LocalDumps key
  4. Add a new DWORD value under the GlassWire.exe key. Value name “DumpType”, value 2
  5. Add a new STRING value under the GlassWire.exe key. Value name “DumpFolder”, value “C:\users\\Desktop”
  6. Wait for another crash of GlassWire.exe. The dump file will be created on the Desktop.
  7. Send the dump file to us under our “bugs” email if possible.
    https://www.glasswire.com/contact/

Thanks!

I just wanted to chime in with an update. So I’ve been leaving Glasswire running only in the system tray as the workaround, as honestly it is not a big deal. Anyway I saw the post regarding the registry tweaks, so I did that and tried whenever I could remember to leave Glasswire up at midnight so it would crash. Well luck would have it now that it no longer appears to crash.

I made no major changes to the server, just the usual Windows Updates, so I don’t know if any of them affected it. Either way it appears to no longer be an issue for me. Also, I ended up buying Pro earlier today, I saw the promo on Neowin to get it for $24, I couldn’t pass it up.

1 Like

We just released an update this morning that fixes the midnight crash. Is that the update you’re using? If not we recommend you upgrade.

I forgot to mention that I have been running .39b since I mentioned in earlier post. I’ll update the version and see what happens. Thank you again

1 Like