Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0027011Openbravo ERPA. Platformpublic2014-07-03 23:192014-08-06 14:32
Reporteregoitz 
Assigned Tojonalegriaesarte 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Toegoitz
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression levelProduction - Confirmed Stable
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0027011: Memory leaks using new selector on old parameters popus
DescriptionMemory leaks using new selector on old parameters popus.
The objects referenced by the selector are loaded in memory, but never cleared.
Steps To Reproduce-Define a new report/process to execute a jrxml
-Define a parameter to use a new partner selector
-Create a menu entry to execute that jasper report
-Compile and restart tomcat.
-Login to the application.
-Open the parameter window select a partner and click on ok button.
*A java process start consuming resources concretely consuming memory.
Proposed Solution
Additional Information
TagsPerformance
Relationships
duplicate of defect 0027088 closed alostale Wrong behavior with obuisel selectors in manual windows 
related to defect 0026911 closed AugustoMauch The request to the datasource are done several times when opening a selector from a 2.50 process popup 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-07-03 23:19egoitzNew Issue
2014-07-03 23:19egoitzAssigned To => AugustoMauch
2014-07-03 23:19egoitzModules => Core
2014-07-03 23:19egoitzResolution time => 1405375200
2014-07-03 23:19egoitzRegression level => Production - Confirmed Stable
2014-07-03 23:19egoitzTriggers an Emergency Pack => No
2014-07-03 23:19egoitzTag Attached: Performance
2014-07-03 23:19egoitzRelationship addedrelated to 0026911
2014-07-03 23:20egoitzPriorityurgent => immediate
2014-07-03 23:20egoitzSeveritymajor => critical
2014-07-04 18:04jecharriIssue Monitored: jecharri
2014-07-08 14:33ngarciaIssue Monitored: ngarcia
2014-07-15 11:32shuehnerIssue Monitored: shuehner
2014-07-17 11:01dmitry_mezentsevRelationship addedduplicate of 0027088
2014-07-17 11:05dmitry_mezentsevNote Added: 0068693
2014-07-17 11:05dmitry_mezentsevAssigned ToAugustoMauch => jonalegriaesarte
2014-07-17 11:05dmitry_mezentsevStatusnew => feedback
2014-07-22 10:01dmitry_mezentsevNote Added: 0068782
2014-07-22 10:01dmitry_mezentsevPriorityimmediate => high
2014-07-22 10:01dmitry_mezentsevSeveritycritical => major
2014-07-22 10:05dmitry_mezentsevResolution time1405375200 =>
2014-07-22 10:05dmitry_mezentsevNote Added: 0068784
2014-07-24 12:29jonalegriaesarteResolution time => 1407708000
2014-08-06 14:26egoitzReview Assigned To => egoitz
2014-08-06 14:26egoitzStatusfeedback => closed
2014-08-06 14:26egoitzResolutionopen => duplicate
2014-08-06 14:32ngarciaIssue End Monitor: ngarcia

Notes
(0068693)
dmitry_mezentsev   
2014-07-17 11:05   
From what I understood the issue dsc is not enough to reproduce it and there is no enough info in the ticket.
Apart from it we consider that issue 0027088 might be about the same and this one is fixed.
(0068782)
dmitry_mezentsev   
2014-07-22 10:01   
Cannot be Critical and without feedback
(0068784)
dmitry_mezentsev   
2014-07-22 10:05   
Removing resolution time as the current one is outdated