As another attempt for rational explanation (silly thing without code sample and error message), you may have inadvertently put call to slurp into list context, like:

which then tries to split 5e8 bytes to presumably quite short lines, and may consume a few of 1e9 bytes of RAM long before JSON complains about wrong usage.