It's probable unrelated to size as expected.

For the record: 

I've changed the  XMLParser and the new one complained about a problem on a specific line that has this content

<sixx.object sixx.id="1106" sixx.name="key" sixx.type="String" >name</sixx.object>
<sixx.object sixx.id="1107" sixx.name="value" sixx.type="String" >&#0;&#0;&#0;L&#0;&#0;&#0;i&#0;&#0;&#0;k&#0;&#0;&#0;e&#0;&#0;&#0; &#0;&#0;&#0;M&#0;&#0;&#0;a&#0;&#0;&#0;r&#0;&#0;&#0;k&#0;&#0;&#0; &#0;&#0;&#0;T&#0;&#0;&#0;w&#0;&#0;&#0;a&#0;&#0;&#0;i&#0;&#0;&#0;n&#0;&#0;&#0;:&#0;&#0;&#0; &#0;&#0; &#28;&#0;&#0;&#0;I&#0;&#0;&#0;&apos;&#0;&#0;&#0;v&#0;&#0;&#0;e&#0;&#0;&#0; &#0;&#0;&#0;n&#0;&#0;&#0;e&#0;&#0;&#0;v&#0;&#0;&#0;e&#0;&#0;&#0;r&#0;&#0;&#0; &#0;&#0;&#0;l&#0;&#0;&#0;e&#0;&#0;&#0;t&#0;&#0;&#0; &#0;&#0;&#0;m&#0;&#0;&#0;y&#0;&#0;&#0; &#0;&#0;&#0;s&#0;&#0;&#0;c&#0;&#0;&#0;h&#0;&#0;&#0;o&#0;&#0;&#0;o&#0;&#0;&#0;l&#0;&#0;&#0; &#0;&#0;&#0;i&#0;&#0;&#0;n&#0;&#0;&#0;t&#0;&#0;&#0;e&#0;&#0;&#0;r&#0;&#0;&#0;f&#0;&#0;&#0;e&#0;&#0;&#0;r&#0;&#0;&#0;e&#0;&#0;&#0; &#0;&#0;&#0;w&#0;&#0;&#0;i&#0;&#0;&#0;t&#0;&#0;&#0;h&#0;&#0;&#0; &#0;&#0;&#0;m&#0;&#0;&#0;y&#0;&#0;&#0; &#0;&#0;&#0;e&#0;&#0;&#0;d&#0;&#0;&#0;u&#0;&#0;&#0;c&#0;&#0;&#0;a&#0;&#0;&#0;t&#0;&#0;&#0;i&#0;&#0;&#0;o&#0;&#0;&#0;n&#0;&#0;&#0;.&#0;&#0; &#29;</sixx.object>
</sixx.object>

looks like an encoding problem



On Jan 3, 2014, at 5:59 PM, Sebastian Sastre <SEBASTIAN@FLOWINGCONCEPT.COM> wrote:

Hi guys,

anyone here using SIXX?

I'm having a consistent problem in opening a SixxReadStream on a file that has ~10MB of serialized objects.

Smaller than that is all good

Bigger, raises SixxXmlParseError

ideas? 

Maybe I'm using the wrong version of XMLDOMParser?

patches? workarounds?

PD: sixx was loaded with:

Gofer it
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfSIXX';
load.

(Smalltalk at: #ConfigurationOfSIXX) project latestVersion load.