#18 sf_tracker_export.php XML output problem

[Kevin Altis]

This issue was initially reported to sourceforge.net:
http://sourceforge.net/tracker/?
func=detail&atid=424533&aid=498835&group_id=39306

but I was told that is an alexandria-dev issue, so I'm
resubmitting it here.

Since I first posted this bug I also realized that the
XML returned is not valid. The issue is described here:
http://aspn.activestate.com/ASPN/Mail/Message/xml-
sig/967244

There should be a header such as:

<?xml version="1.0" encoding="iso-8859-1"?>

Apologies in advance if this is still the wrong forum
for reporting the bug.

ka
---

I regularly download the XML for various projects
tracker items. In the past I've been unable to
download the Python bug list from

http://sourceforge.net/export/sf_tracker_export.php?
atid=105470&group_id=5470

because the download would always time out. When I
browse the bugs it shows:

Bugs ( 180 open / 2042 total )

http://sourceforge.net/tracker/?
atid=105470&group_id=5470&func=browse

Today however, I started to get the XML file and then
the transfer died in mid-stream. When I checked the
end of the XML file I found

<b>Fatal error</b>: Allowed memory size of 8388608
bytes exhausted (tried to allocate 35 bytes) in
<b>/usr/local/sourceforge.net/www/export/sf_tracker_exp
ort.php</b> on line <b>82</b><br>

So, it appears that the problem is that the
sf_tracker_export.php script is probably attempting to
build the entire XML file in memory (DOM maybe) rather
than outputting from the database as a SAX stream (or
something less memory intensive).

Anyway, it would be nice to be able to download the
Python bug list in XML format. I'm sure this problem
applies to other big projects with large bug and
feature lists too.

Thanks,

ka
---
Kevin Altis
altis@semi-retired.com