Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000950Openbravo ERPB. User interfacepublic2007-03-06 14:082009-01-30 15:32
Reporteruser71 
Assigned Toshuehner 
PriorityurgentSeveritytrivialReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Versionpi 
Target VersionpiFixed in Versionpi 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0000950: Unclosed javascript objects
DescriptionThere are javascript objects in many windows that are not closed. This creates memory leaks.
Steps To Reproduce
Proposed SolutionReview Javascript objects in order to avoid memory leaks.
Additional Information
TagsPerformance
Relationships
related to feature request 0007271 closed shuehner Analyse / Check javascript memory usage 
depends on backport 0006096pi closed shuehner Unclosed javascript objects 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-06-13 19:12cromeroPrioritynormal => low
2008-06-13 19:12cromeroSeverityminor => trivial
2008-06-13 19:12cromeroStatusnew => scheduled
2008-06-13 19:58cromeroTarget Version => 2.40
2008-07-02 11:20pjuvaraNote Added: 0008123
2008-07-02 11:20pjuvaraPrioritylow => normal
2008-07-07 21:05dbazNote Added: 0008196
2008-07-07 21:05dbazStatusscheduled => feedback
2008-07-08 00:10cromeroNote Added: 0008207
2008-07-08 00:10cromeroStatusfeedback => new
2008-07-08 11:17plujanNote Added: 0008215
2008-07-14 08:52cromeroStatusnew => acknowledged
2008-11-03 12:18rafarodaTypedefect => feature request
2008-11-03 12:18rafarodaSteps to Reproduce Updated
2008-11-03 12:18rafarodaTag Attached: Performance
2008-11-15 13:44pjuvaraNote Added: 0010298
2008-11-15 13:44pjuvaraTypefeature request => defect
2008-11-15 13:44pjuvaraTarget Version2.40 => trunk
2008-11-20 10:45rafarodaStatusacknowledged => scheduled
2008-11-20 10:45rafarodafix_in_branch => trunk
2008-11-20 10:46rafarodaNote Added: 0010432
2008-12-03 01:19dbazAssigned Todbaz => shuehner
2008-12-03 01:20dbazNote Added: 0010924
2009-01-19 12:47rafarodaversion => trunk
2009-01-19 12:47rafarodafix_in_branchtrunk =>
2009-01-29 11:53pjuvaraPrioritynormal => urgent
2009-01-30 15:25shuehnerRelationship addedrelated to 0007271
2009-01-30 15:32shuehnerRegression testing => No
2009-01-30 15:32shuehnerStatusscheduled => closed
2009-01-30 15:32shuehnerNote Added: 0012914
2009-01-30 15:32shuehnerResolutionopen => no change required

Notes
(0004539)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:43)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1674794 [^]
(0008123)
pjuvara   
2008-07-02 11:20   
Bumping up priority since this defect has been open for a long time.
(0008196)
dbaz   
2008-07-07 21:05   
I don't know what the bug means.

I need an explanation and an example.
(0008207)
cromero   
2008-07-08 00:10   
Try installing any of these tools that informs about memory leaks:
* Leak Monitor - https://addons.mozilla.org/firefox/2490/ [^]
* Drip - http://outofhanwell.com/ieleak/index.php?title=Main_Page [^]
* JavaScript Memory Validator - http://www.softwareverify.com/javascript/memory/index.html [^]
(0008215)
plujan   
2008-07-08 11:17   
David, you will found some handy data here:
http://www-128.ibm.com/developerworks/web/library/wa-memleak/ [^]

You should also verify this with JAL and other whom performed some performance and stress testing on OB, since a leakage would be obvious in that context.
(0010298)
pjuvara   
2008-11-15 13:44   
Not sure why this was changed to feature request. There is no additional feature requested here but simply fixing existing behavior.
(0010432)
rafaroda   
2008-11-20 10:46   
Reminder sent to: dbaz

This is a reminder for Dbaz
(0010924)
dbaz   
2008-12-03 01:20   
Hi Stefan.

I assign to you this bug because is quite old and I can't success solving it.

Let's try if you can achieve any solution.

Thanks
(0012914)
shuehner   
2009-01-30 15:32   
This issue failed to point to a single real defect but just raises a general: do audit javascript usage for potential memory problems.

We created the feature request 7271 to address this audit/test. and do close this issue as is not a defect.