Memory leak in streaming parser

4 Apr
2007
4 Apr
'07
1:39 a.m.
I refactored the code and uploaded a new version to Hackage (YamlReference-0.2). It is cleaner now and much more efficient. It is still "leaking" memory though. The profiler hints at "bindReply" as the culprit retaining State and Reply objects, but it isn't clear to me why the code would do that. Trying to `seq` things again either kills streaming or has no effect. Perhaps my basic approach is wrong... Any advice would be appreciated, Oren Ben-Kiki
6622
Age (days ago)
6622
Last active (days ago)
0 comments
1 participants
participants (1)
-
Oren Ben-Kiki