bug #7047
Vaadin UI and View scope beans are not always destroyed correctly
100%
Description
while examining problems related to the connection pool runnig out of available connections it turned out that Vaadin UI and View scope beans are not always destroyed correctly once the view or UI was no longer used.
One problem was caused by the LoginViewBean being in UIScope. This issue has been solved meanwhile with cdm-vaadin|157c9c3 but it seems as if some views and presenters are still never being disposed and garbage collected correctly. This can potentially cause the vaadin UIs to eat up all memory over long time.
Related issues
Associated revisions
ref #7036 LoginView in View scope helps disposing this bean
it is no longer required to have it in the UIScope
History
#1 Updated by Andreas Kohlbecker over 1 year ago
- Related to bug #7036: correctly release vaadin view resources when the browser windows has been closed added
#2 Updated by Andreas Kohlbecker over 1 year ago
- Related to bug #6687: Multiple representations of the same entity merge problem added
#3 Updated by Andreas Kohlbecker over 1 year ago
- Related to bug #7046: replace open session per view pattern by DTO strategy added
#4 Updated by Andreas Kohlbecker over 1 year ago
- Related to deleted (bug #7036: correctly release vaadin view resources when the browser windows has been closed)
#5 Updated by Andreas Kohlbecker over 1 year ago
- Duplicates bug #7036: correctly release vaadin view resources when the browser windows has been closed added
#6 Updated by Andreas Kohlbecker over 1 year ago
- Duplicates deleted (bug #7036: correctly release vaadin view resources when the browser windows has been closed)
#7 Updated by Andreas Kohlbecker over 1 year ago
- Related to bug #7036: correctly release vaadin view resources when the browser windows has been closed added
#8 Updated by Andreas Kohlbecker over 1 year ago
- File Vaadin-Bean-Destroy-Breakpoints.bkpt added
#9 Updated by Andreas Kohlbecker over 1 year ago
- Priority changed from New to Priority11
#10 Updated by Andreas Kohlbecker 10 months ago
- Related to bug #7742: vaadin view presenters not disposing ehcaches and object references in event bus which can cause memory leaks added
#11 Updated by Andreas Kohlbecker 10 months ago
- Description updated (diff)
- Status changed from New to Feedback
- Target version changed from Unassigned CDM tickets to Release 5.3
this should also be fixed now that #7742 is solved
#12 Updated by Andreas Kohlbecker 10 months ago
- Status changed from Feedback to Resolved
#13 Updated by Andreas Kohlbecker 10 months ago
- Target version changed from Release 5.3 to Release 5.4
The RegistrationWorkingsetPresenter, LoginPresenter and RegistationUI still are not destroyed correctly. At least RegistrationWorkingsetPresenter still seems to be registered to the view event bus.
Is this a session timeout issue?
#14 Updated by Andreas Kohlbecker 10 months ago
- Status changed from Resolved to In Progress
#15 Updated by Andreas Kohlbecker 10 months ago
Andreas Kohlbecker wrote:
The
RegistrationWorkingsetPresenter,LoginPresenterandRegistationUIstill are not destroyed correctly. At leastRegistrationWorkingsetPresenterstill seems to be registered to the view event bus.Is this a session timeout issue?
after ~1h the above mentioned beans have been destroyed with the VaadinSession
#16 Updated by Andreas Kohlbecker 9 months ago
- Priority changed from Priority11 to Highest
#17 Updated by Andreas Kohlbecker 9 months ago
- Target version changed from Release 5.4 to Release 5.5
this should be fixed mean while according to the examination made for #7824
I am leaving this issue open to be confirmed very soon.
#18 Updated by Andreas Müller 9 months ago
if you think it is fixed shouldn't we set it to resolved and keep in 5.4 milestone? So we remember it as being primarily a review ticket. If not fully fixed we can still move it to next version, if fixed we simply close it.
#19 Updated by Andreas Kohlbecker 9 months ago
- Status changed from In Progress to Closed
- Target version changed from Release 5.5 to Release 5.4
- % Done changed from 0 to 100
this has been solved by the changes made for #7036
