Opened 14 years ago
Closed 14 years ago
#2707 closed defect (wontfix)
memory leak in dojo charting
Reported by: | guest | Owned by: | Tom Trenka |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Charting | Version: | 0.4.2 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Hi,
I want to implement a monitoring app using dojo charting
I have made a small prototype that updates a chart based on a timeout the app is constantly leaking memory.
pb reproduced with 0.4.2 rc2 on FF2.0 test case attached to the defect.
to reproduce, click on the 'live chart leak' button
You need the fix described in defect 2706 to make the application work
Thanks
Yann
Attachments (1)
Change History (5)
Changed 14 years ago by
Attachment: | chart_leak.html added |
---|
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
I have investigated. This fix in the Chart.render() function improves things (but it still leaks...)
if (this.node.firstChild){ this.node.replaceChild(node, this.node.firstChild);
area.render();
}else{
this.node.appendChild(node);
}
comment:3 Changed 14 years ago by
Component: | General → Charting |
---|---|
Owner: | changed from anonymous to Tom Trenka |
comment:4 Changed 14 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Closing this because the port of charting to DojoX includes a rewrite to base it on the DojoX GFX engine, so that no directly manipulation of nodes will be happening.
btw feel free to add this test program to the tests delivered with dojo. I think it is actually simpler than the test delivered and useful to help understand the charting api