Page is Freezing in author mode

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. 

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.

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. 

Hi 

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

Thanks,

M.L.Raghava Reddy

Hi,

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

Thanks,

M.L.Raghava Reddy

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 

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. 

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.

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