Accidentally Importing Many Connections - App Unresponsive

Got a problem with Viscosity or need help? Ask here!

blaffy2024

Posts: 2
Joined: Thu Sep 12, 2024 12:59 am

Post by blaffy2024 » Thu Sep 12, 2024 1:10 am
I went to import a connection yesterday, and while browsing the filesystem through the import tool, I accidentally double clicked a folder in an attempt to open it. However, Viscosity took this as me wanting to import that folder (and subsequent subfolders) and since I happened to be near the root directory of my work HDD, ended up importing 100+ connections simultaneously.

After several minutes of being unresponsive, it seemed to import them all successfully, and I was able to remove the unnecessary ones from my connections list. However, the next day when I went to connect again, Viscosity crashed and upon relaunching it, it began consuming many GBs of RAM and never becoming responsive forcing me to kill the process.

How can I return the app to a factory clean state?

I suggest adding a confirmation box when more than 10 or so connections are being imported at once. Bulk import is certainly useful, but it's very easy to accidentally import a whole filesystem's worth of VPN configs with a poorly placed double click.

blaffy2024

Posts: 2
Joined: Thu Sep 12, 2024 12:59 am

Post by blaffy2024 » Thu Sep 12, 2024 5:47 am
UPDATE:

I looked in ~/Library/Application Support/Viscosity/OpenVPN and found 30,000 (!) folders that had been generated yesterday between 7:49PM and 10:16PM. Not sure how that happened, as I had already deleted the extra connections (there should have only been around 100) and wasn't actively using the computer during this time. Please let me know if there are logs or something I can provide so you can get an idea what could have happened here.

After deleting these 30,000 files, the application is running normally again
Last edited by blaffy2024 on Thu Sep 12, 2024 5:58 am, edited 1 time in total.
2 posts Page 1 of 1