I am facing strange issue. sidekick is taking lot of time to load and whole page is getting stuck. I am using chrome and deleted cache n number of times and restarted the system twice.
Pls help me out
Solved! Go to Solution.
Views
Replies
Total Likes
Looks as if someone loaded content or changed content under /libs that caused a JS failure.
Views
Replies
Total Likes
Is this happening for every one or only with you??
Views
Replies
Total Likes
Here are some questions:
1 - what is the RAM of the machine you are using
2 - Did you make any changes under libs
3 - did this just start happening?
If you install a fresh install of CQ - you will see this is not an issue.
Views
Replies
Total Likes
please debug using the browser and see the timeline tab to see what is more time. From there we can start looking at the root cause
Views
Replies
Total Likes
This happens when there is a javascript failure. You might have to look into browser console and check if there is any javascript error.
Jitendra
Kishore@CQ wrote...
Is this happening for every one or only with you??
Happening for every one in my team only on today :(
Views
Replies
Total Likes
Jitendra S.Tomar wrote...
This happens when there is a javascript failure. You might have to look into browser console and check if there is any javascript error.
Jitendra
Thanks a lot for the inputs mate :)
Views
Replies
Total Likes
Jitendra S.Tomar wrote...
This happens when there is a javascript failure. You might have to look into browser console and check if there is any javascript error.
Jitendra
Thanks Jitender for the valuable inputs
Views
Replies
Total Likes
smacdonald2008 wrote...
Here are some questions:
1 - what is the RAM of the machine you are using
2 - Did you make any changes under libs
3 - did this just start happening?
If you install a fresh install of CQ - you will see this is not an issue.
RAM is 8 GB and dint make any changes in libs and it just happened suddenly. After fresh installation issue got resolved. But want to know the real issue.
Views
Replies
Total Likes
Looks as if someone loaded content or changed content under /libs that caused a JS failure.
Views
Replies
Total Likes