Skip to main content

Filter by idea status

10000+ Ideas

System instability via 100% CPU/high RAM usage with Windows ChromeDelivered

Hi Jon/Team,I'd previously sent you a direct email about this, but figured I'd submit it this new way as well.I keep noticing that after having the Chrome extension enabled, and opening and closing enough tabs, eventually all the cores of my CPU spike to 100% and RAM usage goes through the roof. When I pop open Chrome’s Task Manager specifically, I can see that the extension is using 200%+ of the CPU (guess that means multiple cores?). Simply disabling the extension and then re-enabling it drops CPU usage down to single digits and restores RAM usage to a sensible level. (Side note: you can ignore the “Extension: Page Analytics (by Google)” part in the example screenshot below; I’ve also seen the “Adobe Experience Platform Debugger” with “LastPass: Free Password Manager”. It seems like the common Task with the spike is the AEPD extension)The unfortunate side effect here is that if I don’t catch the issue quick enough, it can cause system wide performance issues. I’ve even seen it crash the graphics drivers (when all the memory gets used up) and that throws application windows all over the place (changes their size and monitor placement) when the graphics drivers are restarted. 😞Heh, I should probably mention that I really like the new version … even with the issue I’m seeing! 🙂If there’s anything I can do to help you with the issue I see, please let me know!  

KevinEy2Level 2

Move multiple pagesInvestigating

Request for Feature Enhancement (RFE) Summary: It would be excellent if multiple pages under one path could be selected and moved together. Currently only one page can be selected and moved at a time. It seems like the interface and behind-the-scenes processing is already capable of most of the heavy lifting, as a page with hundreds of children can be moved; just not multiple individual pages. Use-case: This feature would be a huge time-saver in situations like: breaking a section of a site into multiple sections closing down a section of a site and redistributing the child pages among a few remaining sections breaking a small news or event hierarchy into a more robust by-year or by-month structure (e.g. sorting 100 articles into 2020, 2021, 2022 folders) moving lots of pages into a folder (e.g. move 100 pages under a new "archived" page) Current/Experienced Behavior: When selecting one page, a "Move" button appears in the toolbar. When selecting more than one, "Move" disappears. Improved/Expected Behavior: When selecting more than one page, "Move" should keep showing. When used, the rest of the interface for choosing the destination, reviewing and updating references will work as-is. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP12 Customer-name/Organization name: University at Buffalo Screenshot (if applicable):   Code package (if applicable):  

jdavenport-qantasNew Participant

Improve user groups UI in AEM 6.5 Touch UIDeclined

Request for Feature Enhancement (RFE) Summary: Improve the UI of user group management in Touch UI Use-case: Authors managing user permissions Current/Experienced Behavior: Current UI can be confusing and hard to read Improved/Expected Behavior: New UI is simplified and made less confusing Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP 13 Customer-name/Organization name: Qantas   In 6.5 the group management UI can be very confusing compared to 6.3. The UI by default shows all group memberships, including those inherited by other groups. This can be surprising compared to 6.3 which only shows explicit memberships and it makes it a lot less clear what groups the user belongs to. Additionally, the only visual distinction between assigned and inherited group memberships is that the remove button is greyed out on the latter, which is visually very difficult to tell apart and is a bad indicator of which one is which.   I'd like to propose two different solution for this: 1) Instead of greying out the remove button on inherited groups, the button should just be hidden altogether. That would make it very clear which groups can and can't be removed manually. 2) Add a checkbox to filter out the inherited groups. I'd suggest making this disabled by default so it mirrors the 6.3 functionality, then users can optionally check it in order to view the inherited groups that a user has.   Current 6.5 UI (it is very hard to visually distinguish the valid and invalid remove buttons). 6.5 UI with buttons removed (as you can see it is far easier to tell which groups are removable. To improve the UI layout maybe the explicit groups can be sorted to the top so that the buttons aren't at random intervals)    

PT6New Participant

Bulk edit not supported warning after select allDeclined

Request for Feature Enhancement (RFE) Summary: Related Case #E-000797571 Use-case: We noticed recently the new warning message added to AEM bulk edit scenario, where user attempt to “Select all” and edit these sub-pages in separate tabs. The warning message says that “Bulk action not supported, The selected action Edit(e) will only have effect X selected items currently loaded…”. As we understand, the justification for that warning message is to let user know that not all sub pages might have been lazy-loaded, and that’s fine. That also explains why the massage doesn’t need to appear when pages have been selected manually. The point is that the mentioned logic might be confusing when there are only few sub-pages to be selected by “select all”. In that case lazy logic is not the case and user can be sure that “select all” picks all the sub pages we have on the screen. Please consider extending that logic, because our customers feels uncomfortable with new behavior and confusing warning. (More detail you can find in thread for Case #E-000797571) Current/Experienced Behavior: Warning message for few pages selected by "select all" Improved/Expected Behavior: For the scenario when only few sub pages exist, warning message is not necessary, even if pages were selected by "select all"  Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager (6.5.15.0) Customer-name/Organization name: Wundenmanthompson's customer Screenshot (if applicable):   Code package (if applicable):