QueryBuilder Crashing on Chrome & Safari | Community
Skip to main content
TheBigRed
Level 4
December 1, 2015
Solved

QueryBuilder Crashing on Chrome & Safari

  • December 1, 2015
  • 3 replies
  • 1100 views

Hello All,

I'm having an issue where browser is crashing whenever searching for an Asset.

I'm using a search bar which is connected to a servlet that's utilizing the API.

Servlet also contained as an osgi bundle.

However this works amazing on Firefox. Any thoughts or solutions?

 

 

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by kautuk_sahni

Hi

Please try some Quick steps and check if things persists:-

1.  You can use the query builder debugger to play around with the query builder,http://localhost:4502/libs/cq/search/content/querydebug.html?charset=UTF-8&query=path%3D%2Fcontent%0D%0Agroup.p.or%3Dtrue%0D%0Agroup.1_type%3Dcq%3APage%0D%0Agroup.2_type%3Ddam%3AAsset%0D%0A%0D%0A

2. Please try opening an Incognito Windows (Chrome menu button New incognito window) and check the same behavior.

As mentioned by Praveen, it could be a memory issue.

Please share some more information to understand the issue.

Thanks and Regards

Kautuk Sahni

3 replies

Ratna_Kumar
Level 10
December 1, 2015

Which version of Chrome you are using?

Thanks,
Ratna Kumar.

edubey
Level 10
December 2, 2015

Hi,

In which format you are returing data?

What is amount of data?

It might have something with JS that is used for request and response

Thanks

kautuk_sahni
Community Manager
kautuk_sahniCommunity ManagerAccepted solution
Community Manager
December 2, 2015

Hi

Please try some Quick steps and check if things persists:-

1.  You can use the query builder debugger to play around with the query builder,http://localhost:4502/libs/cq/search/content/querydebug.html?charset=UTF-8&query=path%3D%2Fcontent%0D%0Agroup.p.or%3Dtrue%0D%0Agroup.1_type%3Dcq%3APage%0D%0Agroup.2_type%3Ddam%3AAsset%0D%0A%0D%0A

2. Please try opening an Incognito Windows (Chrome menu button New incognito window) and check the same behavior.

As mentioned by Praveen, it could be a memory issue.

Please share some more information to understand the issue.

Thanks and Regards

Kautuk Sahni

Kautuk Sahni