[dotNetRDF-Develop] Issue CORE-378 has a new comment

[<tr...@do...>]

<p>A new comment has been added to the following issue.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>RDF/XML parser can OOM even in streaming mode</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Date:</b></td>
    <td>2013-10-15 11:30 AM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	So the specific problem appears to be in the top level grammar production, it gathers all the events under the top level rdf:RDF element into a single event list and then passes it down to the next production. &nbsp;This has the effect of pre-caching all the data even when running in streaming mode hence the OOM when run against large files.</p>
<p>
	The fix appears to be to introduce a wrapper event list which creates the illusion of being a new event list while really just wrapping the underlying event list and cutting off once the size of the underlying list drops below a given threshold. &nbsp;This should reduce memory usage for both the streaming and DOM parsing modes.</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=378" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=378</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>