-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak for actions instantiated through AbstractActionWrapperHandler #174
Comments
Analysis: The selection of this kind of actions is changed just before the execution of the action, in So a solution is to reset the selection just after the execution. |
The selection, of actions launched through AbstractActionWrapperHandler, was never cleaned. This commit cleans up the selection just after using it. Bug: #174
As the previous commit, the command FindElementCommand has the same memory leak pattern, but without inherited from AbstractActionWrapperHandler. Bug: #174
The PR #175 solves the problem. With this PR, in the initial steps to reproduce, the observed memory leak is no longer here. It remains another leaks on |
Additional analysis: There is only "one memory leak" per action. Indeed, only one instance of this kind of actions is created during the first need. For example, in the scenario of this issue, the
|
The selection, of actions launched through AbstractActionWrapperHandler, was never cleaned. This commit cleans up the selection just after using it. Bug: #174
As the previous commit, the command FindElementCommand has the same memory leak pattern, but without inherited from AbstractActionWrapperHandler. Bug: #174
The selection, of actions launched through AbstractActionWrapperHandler, was never cleaned. This commit cleans up the selection just after using it. Bug: #174
As the previous commit, the command FindElementCommand has the same memory leak pattern, but without inherited from AbstractActionWrapperHandler. Bug: #174
This issue is a sub part of #144. It concerns actions instantiated through
AbstractActionWrapperHandler
: BringForwardAction, BringToFrontAction, DeleteFromDiagramAction, DeselectAllAction, HideDDiagramElementAction, HideDDiagramElementLabelAction, PinElementsEclipseAction, QuickOutlineAction, RefreshDDiagramElementAction, RefreshAction, RevealAllElementsAction, RevealElementsAction, SendBackwardAction, SendToBackAction, RevealOutlineLabelsAction, SynchronizedDiagramAction and UnpinElementsEclipseAction.Steps to reproduce:
org.eclipse.sirius.tests.swtbot.layout.ZOrderActionsTest
where the leak has been discovered.exceptions=off,disablestacktelemetry,alloceach=100,allocsizelimit=4096
to have memory analysis enabled)My.ecore
androot
diagramWithNodesAndEdges
edge1
, launch the actionBring to Front
(from contextual menuFormat>Order
)Edit>Undo
DDiagramEditorImpl
referenced through theselection
ofBrintToFrontAction
.The text was updated successfully, but these errors were encountered: