Hide Forgot
Description of problem: Saving certain types of assets (e.g. models, dsl configurations, not rules) causes a significant peak in browser's CPU usage. From the user's point of view the browser simply freezes for a period of time. Duration of the peak load and memory usage increases with the number of continuous save operations, where 'continuous' means without logging out and back in. Version-Release number of selected component (if applicable): BRMS 5.3.0.DEV5 How reproducible: always Steps to Reproduce: 1. import mortgage sample repo; open ApplicantDsl 2. keep saving it repeatedly until browser response time becomes uncomfortable (~10 rounds) 3. after logging out, browser memory usage drops Actual results: It's not possible to work in Guvnor continuously without relogging if you save models and DSL configurations (maybe other asset types too) often. Expected results: Guvnor's resources (CPU, memory) demand shouldn't depend on the number of performed save operations. User shouldn't be forced to relog in order to continue working. Additional info:
My guess is that the suggestion completition engine is doing too much or leaking memory.
To add the logging to every service call, we 'll have to create a simple "AbstractGuvnorServlet (or Service)" and let all our guvnor services extend that. Then put an Interceptor on it that only activates during development to log it. Seam doesn't provide such an Interceptor out of the box, but it should be easy to write (and to contribute back to seam).
I just noticed a mistake in the description (expected results) and I don't know how to edit it. Just s/Guvnor/Browser/. It's the browser that is consuming more and more CPU and memory. Seems like there's a poor JavaScript code on the client side.
Confirming the regression, couldn't reproduce with 5.2.
Please verify the issue on 5.3 ER4.
Couldn't reproduce in ER6, so I consider this issue fixed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously when saving assets in the BRMS user interface, the browser CPU usage spiked and from a user's perspective the browser appeared to freeze. This issue was present in JBoss BRMS 5.2.0, however, is not present in JBoss BRMS 5.3.0.