Linkedin Showing anomaly on Chrome and Mozilla
I am not sure whether this is happening only on my system or this is also being observed by other user. Whenever I am trying to see the profile of some friend of friend-list or in connection then
1- In Chrome
- It shows one request like WAITING FOR SECURE-US.IMRWORLDWIDE.COM….
- Scroller get stuck and page download does n’t finish even we left for many hours,
- This is happening with those linkedin profile in which person is currently living/working in USA
2- In Mozilla
- A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.
Script: http://127.0.0.1:10029/public/linkchecker.firefox.js:207
- Mozilla become freez and browser start showing No response message on the top of Browser.
Friends I have seen this anomaly in my system and want you all to just verify and if you know some troubleshooting method to come out with this situation then please let me know.
While same thing is working properly in IE browser
Hoping to listen from you
-Regards
Dwarika Dhish Mishra
I have had the same problem. It would be good to see a response on this
I was able to resolve this. I went to chrome store and downloaded the Linkedin extension. This issue is not recurring after that.
Could you tell something in very detail about the Linkedin Extension. What is its relation with common browsing.
Hope to listen from you at earliest
Hi Dwarika, I am not sure how the Linkedin Extension is actually helping. But, here is what I did and its working –
1. Go to Google Chrome WebStore (https://chrome.google.com/webstore/category/home)
2. Search for ‘Linkedin’
3. Under the Extensions section, you will find a Linkedin extension
4. Install the extension and restart Chrome
After this whenever you visit the Linkedin profile pages, the pages are not hanging in Chrome. I have tested this on US and NON-US profiles.
Hope this helps 🙂
Thank you ! Really its working ..but i think we need to investigate further to find out root cause behind this error …since this is happening due to busy script ..we should take it as point of investigation why scripts get so busy and how we can fine tune it.