Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0007271 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| feature request | [Openbravo ERP] A. Platform | minor | have not tried | 2009-01-30 15:21 | 2011-09-21 23:03 | |||
| Reporter | shuehner | View Status | public | |||||
| Assigned To | shuehner | |||||||
| Priority | normal | Resolution | duplicate | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | pi | SCM revision | ||||||
| Merge Request Status | ||||||||
| Review Assigned To | ||||||||
| OBNetwork customer | No | |||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Support ticket | ||||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0007271: Analyse / Check javascript memory usage | |||||||
| Description | There are several tools available to check for wrong javascript patterns, memory leaks for web applications. It could be a good idea, to do a project analyze openbravo's behaviour when checked with these tools. Possible tools/articles mentioned in old issue 950: * 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 [^] [^] * http://www-128.ibm.com/developerworks/web/library/wa-memleak/ [^] [^] | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||||
|
|||||||||||||||
 Relationships |
|
Notes |
|
|
(0041218) shuehner (administrator) 2011-09-21 23:03 |
Marking this old tracking issue for js mem usage as duplicate of a new real situation showing problematic memory increase. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-01-30 15:21 | shuehner | New Issue | |
| 2009-01-30 15:21 | shuehner | Assigned To | => rafaroda |
| 2009-01-30 15:21 | shuehner | sf_bug_id | 0 => 2549226 |
| 2009-01-30 15:21 | shuehner | OBNetwork customer | => No |
| 2009-01-30 15:21 | shuehner | Regression testing | => No |
| 2009-01-30 15:21 | shuehner | Assigned To | rafaroda => shuehner |
| 2009-01-30 15:25 | shuehner | Relationship added | related to 0000950 |
| 2011-09-21 23:03 | shuehner | Relationship added | duplicate of 0018421 |
| 2011-09-21 23:03 | shuehner | Note Added: 0041218 | |
| 2011-09-21 23:03 | shuehner | Status | new => closed |
| 2011-09-21 23:03 | shuehner | Resolution | open => duplicate |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |