21-05-2013 21:44 - edited 21-05-2013 21:58
Skype Click to Call crashes Explorer, Chrome & Firefox on the two computers of mine that I use Skype on. When I open Task Manager I see many mutiple tasks of whichever browser that Im using listed. I wish Skype would investigate this bug and fix it, has been bothering me for months. Only solution is to shut down Skype and restart all browsers. Anyone else grappling with this? I do not want to remove it, I just want it to work right.
Have you tried to uninstall this Click-to-Call add-on?
I have tried to re-install although on instaling the new version I'm told to close down Chrome, Chrome is not open and therefore I have to abort the set up eventually as I cannot close somethingthat is not open. I am having the same problem with uninstall "Click to call".
I am not really able to browse now with Chrome or IE, as it keeps crashing...
Any thoughts would be appreciated.
You can uninstall Chrome >> then uninstall the Click to Call Plugin >> Reinstall Chrome.
Firstly, if you'd asked me a couple of years ago if I would EVER consider IE I would have said "Not only no but HELL NO". But guess what? Chrome is the easiest browser to hack/infect that is out there (not to mention "your" info becomes Google's info just like TwoFaceBook - suggest getting rid of both with extreme prejudice.
I still run Vista on this here machine because it took years to stabilize. With IE9 I've tried all the above and more. Nada. Suggestions? Anyone...anyone? Bueller?...
I am using the latest version and skype click to call on Chrome is still crashing chrome. I just wish I could find an older version that works. Anyone have any ideas? This has been going on for months so I don't trust skype to fix it. I am running windows 8 with the latestet updates to the OS, Skype, Chrome and Skype click to call.
I am running the lastest version of C2C and Chrome and it works, so please don't assume Skype will fix this when Skype may not even be the culprit (it would be a mistake to assume that Skype is at fault just because the issue may have manifested after upgrading Skype -- sounds logical but it isn't)