Page is Freezing in author mode

[lakshmi_raghava]

Hi,

Page is Freezing in the author mode, it's saying stop script or Script is not loading, when we click on stop script page is coming fine. Please help us in this.

Thanks,

M.L.Raghava Reddy. 

[Paul_McMahon]

Do you see any error message in your browser's JavaScript console? Depending on what 3rd party applications you may be including (social media feeds, analytics, other types of integrations) your error may be related to those scripts and not any AEM/authoring related functionality. 

Also how many components/paragraphs are there on the page in questions. Sometimes if there hundreds of components on a page you can see that error since it will take a long time for all the authoring tools to be initialized. 

[Bruce_Lefebvre]

Is this happening on a Geometrixx sample page or a page you developed yourself?

[lakshmi_raghava]

Hi,

Thanks for your reply.

We are getting the page properties errors in our own developed pages and we are getting java script error. Attached the screenshot for your reference.

Please help us to resolving this js error.

[Paul_McMahon]

You guys are going to have to do some JavaScript debugging of you own, there is really no easy answer to this. 

The first place you should look is the JavaScript console in your browser to see if you have any script errors. You can also add ?debugClientLibs=true to your page's URL which will cause each of the JS files from the client library to be rendered individually. This may help track the source of the problem. You will likely have to look at the JavaScript console, and consider setting some breakpoints and debugging your page to find the issue. 

If the issue isn't happening on Geometixx page then that implies that you have a problem in one of your components. It could be almost anything - you could have a bad dialog definition, you could third party javascript that is causing issues on your page, which is in turn causing authoring widgets to react badly. At this point you really need dig in trace down all the JavaScript errors happening on your page, not just the one that is popping up. If you look at your JavaScript console you may see errors other than the error that pops up. This may lead you to the root cause of your problem. 

[lakshmi_raghava]

Hi,

Thanks for your response.

we got the following js errors when we tried with the ?debugClientLibs=true.

TypeError: El._flyweights is undefined
var p = CQ_swfobject.p;
swfobject.js (line 6)
TypeError: CQ.Ext.elCache is undefined
if(!CQ.Ext.elCache[id]){
2
EventManager.js (line 66)200 OK
354ms    HTTP.js (line 158)
uncaught exception: out of memory

Please help me out to resolve this error.

Thanks,

M.L.Raghava Reddy 

[lakshmi_raghava]

Hi,

Can any one, Please provide the solution for this issue.

Thanks,

M.L.Raghava Reddy

[lakshmi_raghava]

Hi 

Any one can you Please provide for the solution for this issue.

Thanks,

M.L.Raghava Reddy

[Paul_McMahon]

Well if you error is accurate the browser is running out of memory when executing the client side code in your page. I have never seen this on a CQ implementation before but I'd say you need to consider the following issues:

• Is your browser machine under powered or low on memory for other reasons
• Do you have too many components on your page - I have seen this before pages with hundreds of components on a page run into client side issues
• Do you have some custom javascript code that is causing a problem that happens to surface later in page execution. 

Again I think your only solution is to get out you JavaScript debugger and look at how many objects are in your DOM and debug the page to try and identify which code in causing the problem. There is no simple solution to your problem - it can probably on be fixed by debugging you instance. 

[davidf46996755 · Accepted solution]

Do you have your own Javascript running on the page? If so, try disabling it to determine if the problem is in your code. If the problem is in your Javascript code then you can try disabling it piece by piece to further isolate the problem.

Are there any failed requests for Javascript files in the browser? Check the Network tab in your browser developer tools to find any broken requests.

[lakshmi_raghava]

David Frenkiel wrote...

Do you have your own Javascript running on the page? If so, try disabling it to determine if the problem is in your code. If the problem is in your Javascript code then you can try disabling it piece by piece to further isolate the problem.

Are there any failed requests for Javascript files in the browser? Check the Network tab in your browser developer tools to find any broken requests.

Hi David,

Thanks for the response and we know the which js file is causing the issue, is it possible to not to load that js file in the author? If possible, Please provide the steps to not to load the js file.

Thanks,

M.L.Raghava Reddy.

[lakshmi_raghava]

Hi David,

Thanks for the response and we know the which js file is causing the issue, is it possible to not to load that js file in the author? If possible, Please provide the steps to not to load the js file.

Thanks,

M.L.Raghava Reddy .

[davidf46996755]

Is it your code or CQ's code?

Lakshmi Raghava Reddy Mannem wrote...

Hi David,

Thanks for the response and we know the which js file is causing the issue, is it possible to not to load that js file in the author? If possible, Please provide the steps to not to load the js file.

[lakshmi_raghava]

yes, it's from our code, which is a js file called, date.js 

[davidf46996755]

To remove/disable the Javascript code you can...

1) Remove date.js from the js.txt file.

2) Delete the contents of date.js.

3) Put comments around everything in date.js.

4) Change its clientlibs "categories" property so that it's no longer included. However, if you're directly referencing date.js in a script include I don't think this will work.

You can quickly try any of these options in CRXDE.

If you still see problems then you should verify that date.js is definitely disabled. You can do this by viewing the source in your browser developer tools or by adding a console.log() or alert() call at the top of date.js.

Clientlibs are cached in CQ so sometimes changes don't take affect. But removing date.js from its js.txt (option 1) should work.

[lakshmi_raghava]

Hi David,

But you can't able to remove that js file,because the js file is referring so many jsps in my code. Other than removing that is there any alternate way for this?

Thanks,

M.L.Raghava Reddy. 

[davidf46996755]

I'm just suggesting that you temporarily remove date.js to determine if the bad code is in date.js.

If you already know that the problem is in date.js then I suggest disabling pieces of date.js so that you can further isolate the problem.

So my suggestions aren't actually going solve the problem. It's just to help find the exact source of the problem.

Once you find the exact source of the problem you can figure out how to fix it.

[lakshmi_raghava]

Hi  David,

Thanks for the response and I know the which part of the code is causing the issue, it's because of the variable declaration in the date js file, I modified the name of the variable also after that there is no Page freze but because of the variable name change, my application was  failed in another place. Can you please help me out in that one, instead of renaming the variable name. 

Thanks,

M.L.Raghava Reddy.

[lakshmi_raghava]

Hi David,

I attached the js file and when I tried to rename the variable names in 82 line, I didn't get the freeze error but my application was failed because of rename of the variable, Please provide the solution.

Thanks,
M.L.Raghava Reddy

[davidf46996755]

Ok great. So you've isolated the problem to a specific piece of Javascript code.

I can't make any recommendations as to how to fix your Javascript code. But if you want to post the code here on the forum I can take a quick look.

[davidf46996755]

Hey so sorry, I can't help you with this. That's a 3rd party Javascript library: http://www.datejs.com. Maybe you can ask them for help.