Yeah, CSV files can have embedded newlines, so you can't just split it
up on linebreaks and expect it to work, you need to send them through
a parser.
parse-csv *is* lazy, so my question is, are you doing this at the
repl, exactly as you wrote? If so, it will lazily parse the file, and
then print that sequence to the repl output, which will consume the
whole sequence, causing it to all be in memory at once, and the
exception you got. It's the same problem as if you do (repeat 10) at
the repl.
If you are instead consuming it lazily (by say assigning it to a
variable and processing it in some way that only consumes as much as
you need of it, or using a function that processes a lazy seq a piece
at a time), then there is a bug in the library, and I'd appreciate it
if you file an issue for me on the repo so we can get it sorted out
ASAP.
David