[JBoss JIRA] (DROOLS-4584) Scrolling during editing mode move cell in new position on the screen
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4584?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-4584:
-------------------------------------
[~manstis] no, it is not.
> Scrolling during editing mode move cell in new position on the screen
> ---------------------------------------------------------------------
>
> Key: DROOLS-4584
> URL: https://issues.jboss.org/browse/DROOLS-4584
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.28.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: CustomerFocus
> Attachments: image-2019-10-01-11-24-36-774.png
>
>
> !image-2019-10-01-11-24-36-774.png|thumbnail!
> Cell moves unexpectedly in editing mode
> {color:red}*Failure*{color}
> If you start edit any cell of a big grid and then scroll the input would move not in the right cell.
> *Expected*
> Input element moves with entire table
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12651) ModuleClassLoaderLocator$CombinedClassLoader created for every request when using default module
by Lin Gao (Jira)
[ https://issues.jboss.org/browse/WFLY-12651?page=com.atlassian.jira.plugin... ]
Lin Gao updated WFLY-12651:
---------------------------
Labels: downstream_dependency (was: )
> ModuleClassLoaderLocator$CombinedClassLoader created for every request when using default module
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-12651
> URL: https://issues.jboss.org/browse/WFLY-12651
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 18.0.0.Final
> Reporter: Matt Robson
> Assignee: Lin Gao
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 19.0.0.Beta1
>
>
> During testing, we collected jmap -clstats to see what existed.
> What we saw was:
> total = 311741
> alive=1, dead=311740
> Of those 311750, 310687 of them are unique ModuleClassLoaderLocator$CombinedClassLoader with the same parent 0x0000000730aa98b8
> 0x000000074db04db0 0 0 0x0000000730aa98b8 dead org/jboss/as/security/plugins/ModuleClassLoaderLocator$CombinedClassLoader@0x00000007f0f58650
> Because they're dead, this is not a leak - but it shows what a new CL is created for every single request which is a huge performance hit.
> The new classloading behaviour is introduced into 7.1 by https://issues.jboss.org/browse/SECURITY-930 / https://issues.jboss.org/browse/JBEAP-6559
> From https://github.com/jbossas/jboss-eap7/pull/925/files#diff-a8665415b9dad30...
> } else
> { mappingInfo.addJBossModuleName(DEFAULT_MODULE); }
> }
> The call(s) to ClassLoaderLocatorFactory.get() check for !jbossModuleNames.isEmpty() but because we now explicitly set the default module, it's never not empty so it gets called on every request.
> ClassLoader moduleCL = null;
> List<String> jbossModuleNames = jai.getJBossModuleNames();
> if (!jbossModuleNames.isEmpty())
> { ClassLoaderLocator locator = ClassLoaderLocatorFactory.get(); if (locator != null) moduleCL = locator.get(jbossModuleNames); }
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months