You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(i.e. not parsing at all, just connecting sourceFile to something else), everything works as expected. This makes me think that the cause of the issue is somewhere in parseBytes.
I've encountered this issue when trying to combine multiple conduits with for_, i.e. something like
and then I triggered the issue even when files was a singleton list. I've not been able to reproduce this with constant singleton lists though, perhaps because of optimization. If files was a dynamic Maybe instead, the issue did not occure.
I'm using stackage's lts-12.5, i.e. xml-conduit-1.8.0.
The text was updated successfully, but these errors were encountered:
mbid
changed the title
Space leak when executing multiple Stream.parseBytes conduits
Space leak when executing multiple Text.XML.Stream.Parse.parseBytes conduits
Aug 9, 2018
I've encountered a weird space leak using
Text.XML.Stream.Parse
. I believe a reasonably minimal example is this:If
large-file.xml
is large enough, this crashes with OOM, even before the second iteration over the file.If the line
is replaced with either
(i.e. only parsing the file once) or
(i.e. not parsing at all, just connecting sourceFile to something else), everything works as expected. This makes me think that the cause of the issue is somewhere in
parseBytes
.I've encountered this issue when trying to combine multiple conduits with
for_
, i.e. something likeand then I triggered the issue even when
files
was a singleton list. I've not been able to reproduce this with constant singleton lists though, perhaps because of optimization. Iffiles
was a dynamicMaybe
instead, the issue did not occure.I'm using stackage's lts-12.5, i.e. xml-conduit-1.8.0.
The text was updated successfully, but these errors were encountered: