Re: Viscosity hangs when connection drops
Posted: Mon Feb 29, 2016 2:44 pm
Hi Eric
With the h/w, there was no offence taken &, as said, I knew in writing that I may have been being pernickety. That said, as Viscosity's typically using ~0.5-2% of the CPU, when working properly of course, then it doesn't inherently appear to be underpowered for the usage - though clearly I'm not attempting to do huge amounts of multitasking along with.
As to what to test, it was primarily that you'd thrown 2 options at me, & it wasn't clear at all if the beta was an attempt to permanently correct the issue & so should be run without the mute 20 or not... ...& as you sensibly need feedback so that you know if there's still any issues then this was the point in questioning.
Not to worry though.
Then, as to where things are now, what's happened twice over the weekend is coming in to find the machine unable to connect at the yellow triangle network connection error (I can't think what it's now called in Win10)... This has happened with both the last stable version & the new beta (both with mute 20) // it requires Viscosity to be killed to resolve & other devices can still connect to the internet // but doesn't cause either high CPU or memory usage.
& lastly, as probably something of an aside, am I correct in thinking that the issue mentioned on iPredator's Twitter feed mentioned on the 20th (https://twitter.com/IPredatorVPN), which I noticed yesterday, relates to the reachability error message?
Now, to be clear, that message has only ever come up spasmodically on initial connecting over the last 3.5 weeks (lasting for anything from a couple of minutes to maybe an hour) // has never been the latest thing in the log at the time when there's been a problem with Viscosity locking up &/or killing the connection // & i started intermittently getting that error around the 5th (predating 1.6)... ...so I naturally assumed that it was an issue at their end since the version of Viscosity being used hadn't changed at that point.
With the h/w, there was no offence taken &, as said, I knew in writing that I may have been being pernickety. That said, as Viscosity's typically using ~0.5-2% of the CPU, when working properly of course, then it doesn't inherently appear to be underpowered for the usage - though clearly I'm not attempting to do huge amounts of multitasking along with.
As to what to test, it was primarily that you'd thrown 2 options at me, & it wasn't clear at all if the beta was an attempt to permanently correct the issue & so should be run without the mute 20 or not... ...& as you sensibly need feedback so that you know if there's still any issues then this was the point in questioning.
Not to worry though.
Then, as to where things are now, what's happened twice over the weekend is coming in to find the machine unable to connect at the yellow triangle network connection error (I can't think what it's now called in Win10)... This has happened with both the last stable version & the new beta (both with mute 20) // it requires Viscosity to be killed to resolve & other devices can still connect to the internet // but doesn't cause either high CPU or memory usage.
& lastly, as probably something of an aside, am I correct in thinking that the issue mentioned on iPredator's Twitter feed mentioned on the 20th (https://twitter.com/IPredatorVPN), which I noticed yesterday, relates to the reachability error message?
Now, to be clear, that message has only ever come up spasmodically on initial connecting over the last 3.5 weeks (lasting for anything from a couple of minutes to maybe an hour) // has never been the latest thing in the log at the time when there's been a problem with Viscosity locking up &/or killing the connection // & i started intermittently getting that error around the 5th (predating 1.6)... ...so I naturally assumed that it was an issue at their end since the version of Viscosity being used hadn't changed at that point.