During stress test of asset search of asset share commons [1], a memory leak or unresolved object issue happened.

Steps to reproduce:

  1. Install AEM6.3, SP1 and CFP2

  2. Install (happens even on 1.4.0)

  3. Install (happens even on 1.4.0)

  4. Create a page "search template" on "Asset Share Commons" on Sites

  5. Run "Search" with any word including blank, hundreds times.

  6. Or run this command:

    # ab -n 100 -c 1 -A admin:admin "http://localhost:4502/content/asset-share-commons/en/light/searchtestpage.html?layout=card&p.offset=0&p.limit=24"

    Even after Full Java GC happens, some objects cannot be released.

    # jcmd 1810 GC.class_histogram | grep AssetResult
    505: 169 6760
    # jcmd 1810 GC.class_histogram | grep AssetResult
    189: 1608 64320

    A heap dump analysis tells a suspect is loaded by org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5 [2].

    2. One instance of "" loaded by "org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5 @ 0x9749d5d0" occupies 1,528,764,960 (78.49%) bytes. The memory is accumulated in one instance of "" loaded by "org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5 @ 0x9749d5d0".

      org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5 @ 0x9749d5d0


AEM 6.3 SP1-CFP2 with Asset Share Commons 1.1.2 and earlier versions.


There was a problem in Asset Share Commons. The QueryBuilder search creates unclosed ResourceResolver.


Update Asset Share Commons to version 1.1.4 or later.

تم ترخيص هذا العمل بموجب الترخيص العام غير المعدل الخاص بالإسناد وعدم التجارة والمشاركة الإصدار 3.0 ‏من ‏‏Creative Commons‏‏  إن بنود Creative Commons لا تشمل منشورات Twitter™‎ وFacebook.

إشعارات قانونية   |   سياسة الخصوصية على الإنترنت