0000950: Unclosed javascript objects - Openbravo Issue Tracking System

(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 (reporter)
2008-07-02 11:20

Bumping up priority since this defect has been open for a long time.

(0008196)
dbaz (developer)
2008-07-07 21:05

I don't know what the bug means.

I need an explanation and an example.

(0008207)
cromero (reporter)
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 (manager)
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 (reporter)
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 (developer)
2008-11-20 10:46

Reminder sent to: dbaz

This is a reminder for Dbaz

(0010924)
dbaz (developer)
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 (administrator)
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.

Issue History
Date Modified	Username	Field	Change
2008-06-13 19:12	cromero	Priority	normal => low
2008-06-13 19:12	cromero	Severity	minor => trivial
2008-06-13 19:12	cromero	Status	new => scheduled
2008-06-13 19:58	cromero	Target Version	=> 2.40
2008-07-02 11:20	pjuvara	Note Added: 0008123
2008-07-02 11:20	pjuvara	Priority	low => normal
2008-07-07 21:05	dbaz	Note Added: 0008196
2008-07-07 21:05	dbaz	Status	scheduled => feedback
2008-07-08 00:10	cromero	Note Added: 0008207
2008-07-08 00:10	cromero	Status	feedback => new
2008-07-08 11:17	plujan	Note Added: 0008215
2008-07-14 08:52	cromero	Status	new => acknowledged
2008-11-03 12:18	rafaroda	Type	defect => feature request
2008-11-03 12:18	rafaroda	Steps to Reproduce Updated
2008-11-03 12:18	rafaroda	Tag Attached: Performance
2008-11-15 13:44	pjuvara	Note Added: 0010298
2008-11-15 13:44	pjuvara	Type	feature request => defect
2008-11-15 13:44	pjuvara	Target Version	2.40 => trunk
2008-11-20 10:45	rafaroda	Status	acknowledged => scheduled
2008-11-20 10:45	rafaroda	fix_in_branch	=> trunk
2008-11-20 10:46	rafaroda	Note Added: 0010432
2008-12-03 01:19	dbaz	Assigned To	dbaz => shuehner
2008-12-03 01:20	dbaz	Note Added: 0010924
2009-01-19 12:47	rafaroda	version	=> trunk
2009-01-19 12:47	rafaroda	fix_in_branch	trunk =>
2009-01-29 11:53	pjuvara	Priority	normal => urgent
2009-01-30 15:25	shuehner	Relationship added	related to 0007271
2009-01-30 15:32	shuehner	Regression testing	=> No
2009-01-30 15:32	shuehner	Status	scheduled => closed
2009-01-30 15:32	shuehner	Note Added: 0012914
2009-01-30 15:32	shuehner	Resolution	open => 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 (reporter) 2008-07-02 11:20	Bumping up priority since this defect has been open for a long time.

(0008196) dbaz (developer) 2008-07-07 21:05	I don't know what the bug means. I need an explanation and an example.

(0008207) cromero (reporter) 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 (manager) 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 (reporter) 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 (developer) 2008-11-20 10:46	Reminder sent to: dbaz This is a reminder for Dbaz

(0010924) dbaz (developer) 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 (administrator) 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.