search

TunnlTo / desktop-app

TunnlTo is a Windows WireGuard VPN client built for split tunnelling.
https://tunnl.to
1.11k stars 53 forks source link

UI does not display correctly after several windows hibernates #137

Closed tamaskan closed 4 months ago

tamaskan commented 5 months ago

After a few Windows-Hibernates, the UI looked like this, but everything still works in the background

tunnl

brendanosborne commented 5 months ago

Thanks for reporting this. What Windows version are you using?

tamaskan commented 5 months ago

Win 10 Pro 22H2 19045.2965

rufflepot commented 5 months ago

I thought I was the only one with this issue and never managed to pinpoint the reason for it. TunnlTo installs correctly but presents an all-white windows when started. I'm running Windows 10 Pro 22H2 too although build 19045.3930. I've tried clearing out all other VPN applications in advance using Windows and Revo Uninstaller.

It starts up like this: image

Feedback, Issues and Settings all work as intended but when I click the Edit button everything turns completely white: image

brendanosborne commented 5 months ago

@rufflepot I don't believe this is the same issue. Did you have an older version of TunnlTo installed at some point? Can you try the following:

  1. Right click on the app somewhere and select "Inspect" from the menu
  2. Select the "Application" tab at the top, then expand "Local Storage" in drop down on the left panel
  3. Select the "https://tauri.localhost/" item
  4. You will see key's and value's in the right pane. Remove all the keys and restart the app.
brendanosborne commented 5 months ago

@tamaskan I'm not able to replicate this. How many times does your computer sleep before it becomes an issue? Can you right click the app and select Inspect > Console tab and see if there are any errors present?

tamaskan commented 5 months ago

After 5 hibernates: "Error code: Out of Memory", refresh-button -> white like above, right click without function

brendanosborne commented 4 months ago

I'm going to close this as I'm unable to replicate and therefore cannot diagnose the issue. This may be isolated to the user's OS install/machine as this is the only reported instance. Will reopen if we see other reports.