Sitefinity 6.2.4900 Chrome glitch - loading 15994 days

Posted by Community Admin on 04-Aug-2018 15:24

Sitefinity 6.2.4900 Chrome glitch - loading 15994 days

All Replies

Posted by Community Admin on 17-Oct-2013 00:00

Hi,

Just wondered if someone can confirm.
I've installed a clean Sitefinity 6.2 on both projectmanagers server and IIS 7.5. 
Clean standard template homepage with navigation widget, language selector and inline-editing turned on.

The Google Chrome (v30) network panel keeps returning the overall load time as 15994 days, while DomContentLoaded is about 680ms. Sitefinity 6.1 or 6.2 beta on same server/browser don't have this issue.

The culprit seems to be the /Sitefinity/Public/Services/Statistics/Log.svc/?pageNodeId=... link, however when browsing it directly in a seperate tab Chrome reports proper loading times.

Posted by Community Admin on 22-Oct-2013 00:00

Hello Jochem,

I have tried to reproduce this problem several times using different scenarios, but without any success. Please check the attached screenshot which demonstrating the behaviour on my side. I am using version 30.0.1599.101 of Google Chrome.

Regards,
Kaloyan
Telerik

Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

Posted by Community Admin on 01-Dec-2013 00:00

Hi,

I can confirm I'm having this issue too. Screenshot attached of Chrome dev tools also reporting same.

Thanks

Posted by Community Admin on 01-Dec-2013 00:00

I can also confirm this is happening on 2 of my Sitefinity 6.2 sites, but not on my 6.1 site, so seems to be a 6.2 issue.

Posted by Community Admin on 06-Dec-2013 00:00

Can we have an update please?

I can't optimise my site speed as this ruins all timescales when debugging.

Gary

Posted by Community Admin on 13-Dec-2013 00:00

I have now raised this as a support ticket!

Posted by Community Admin on 13-Dec-2013 00:00

@Gary will you keep us updated?

I've added this as a #mustnotlookcauseitwillbugme issue

This thread is closed