Ticket #2531819 (accepted defect)

Reporter


J. Shirley
Opened: 02/27/12
Last modified: 09/19/12
Status: accepted
Type: defect

Owner


Luke Smith
Target Release: BACKLOG
Priority: P3 (normal)
Summary: Apparent memory leak (depending upon browser) in DataSchema.XML
Description:

Looking at the gist, depending upon the browser you will see memory consumed and never released until that tab is closed.

This was brought to my attention on IRC from kanzie, who is coming from jQuery and noticed the memory leak there. Isolating it in this test case shows that there is definitely a leak.

In Safari 5.1.3, each test run does not consume any additional memory. It remains completely flat.

Firefox 10.0.2 (latest) shows huge memory growth at each test run that never settles or collects (even after closing the tab).

I believe this may be a result of the native XML parsing, but hoping for an answer :)

Type: defect Observed in Version: 3.4.1
Component: DataSchema Severity: S2 (high)
Assigned To: Luke Smith Target Release: BACKLOG
Location: Library Code Priority: P3 (normal)
Tags: memory leak Relates To:
Browsers: Firefox - Latest,Safari 5.1 - Mac
URL: https://gist.github.com/1917251
Test Information:

Change History

Luke Smith

YUI Contributor

Posted: 03/23/12
  • location changed to Library Code
  • milestone changed to 3.6.0
  • priority changed to P3 (normal)
  • status changed from new to accepted

Luke Smith

YUI Contributor

Posted: 03/23/12

There's always JSON ;)

Seriously, though, if you're fetching XML from an external resource, you can use YQL to translate the XML -> JSON.
http://query.yahooapis.com/v1/public/yql?format=json&callback={callback}&q=select%20*%20from%20xml%20where%20url%3D'http%3A//remote/xml/service/com'
(human readable form: "select * from xml where url='http://remote.xml.service.com'" output as JSONP with callback {callback}

Have a look at the YQL console for the XML table
http://developer.yahoo.com/yql/console/#h=select%20*%20from%20xml%20where%20url%3D%27http%3A//rss.news.yahoo.com/rss/topstories%27

Luke Smith

YUI Contributor

Posted: 04/5/12
  • estimated changed from 0 to 1
  • remaining changed from 0 to 1
  • sprint changed to sprint 1

Luke Smith

YUI Contributor

Posted: 04/6/12
  • sprint changed from sprint 1 to backlog

Jenny Donnelly

YUI Developer

Posted: 07/24/12
  • milestone changed from 3.6.0 to 3.NEXT

Moving from 3.6.0 backlog to 3.NEXT.

Jenny Donnelly

YUI Developer

Posted: 09/19/12
  • milestone changed from 3.NEXT to BACKLOG

Moving from 3.NEXT to BACKLOG.