Opened 12 years ago

Closed 3 years ago

Last modified 3 years ago

#19159 closed Bug (invalid)

loaddata reports DeserializationError instead of MemoryError

Reported by: django@… Owned by: nobody
Component: Core (Serialization) Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


The command loaddata data.json errors with DeserializationError instead of MemoryError.



relevant code is simplejson.load(stream) inside the try:

def Deserializer(stream_or_string, **options):
    Deserialize a stream or string of JSON data.
    if isinstance(stream_or_string, basestring):
        stream = StringIO(stream_or_string)
        stream = stream_or_string
        for obj in PythonDeserializer(simplejson.load(stream), **options):
            yield obj
    except GeneratorExit:
    except Exception, e:
        # Map to deserializer error
        raise DeserializationError(e)

Change History (10)

comment:1 by anonymous, 12 years ago

Component: UncategorizedCore (Serialization)

comment:2 by Łukasz Rekucki, 12 years ago

In Python 3 this could be written as raise DeserializationError from e, but I don't see a better equivalent in Python 2.

comment:3 by anonymous, 12 years ago

i think there's too much going on in the try statement:

        for obj in PythonDeserializer(simplejson.load(stream), **options):
            yield obj

the error arises from simplejson.load(stream) when reading a large json file from disk during

comment:4 by Aymeric Augustin, 12 years ago

Triage Stage: UnreviewedAccepted

comment:5 by anonymous, 11 years ago

Possibly fixed by #5423.

comment:6 by Claude Paroz, 11 years ago

No, #5423 is fixing dumpdata, this ticket is about loaddata. The problem with loaddata is that it would be very difficult to incrementally read the file.

comment:7 by Berker Peksag, 10 years ago

json.Deserializer now uses six.reraise (see #18003). I think there are two questions that needs to be answered here:

  1. Should DeserializationError wrap MemoryError? If not, we need a patch to catch MemoryError explicitly.
  2. If yes, the ticket's title and description should be updated.

See also #12007.

comment:8 by Jacob Walls, 3 years ago

Has patch: set
Version: 1.4dev

PR on the assumption we don't want to wrap MemoryError. If we do want to wrap it, we're already chaining the exception with raise from so we can just close the ticket.

comment:9 by Mariusz Felisiak, 3 years ago

Resolution: invalid
Status: newclosed

MemoryError is not wrapped anymore because we no longer use StringIO or BytesIO, and MemoryError is raised by .read() (see 7d0f8831922535502569a5dda989dde339b4e491):

  File "django/django/core/serializers/", line 65, in Deserializer
    stream_or_string =
MemoryError: Problem installing fixture 'mydump.json'

comment:10 by Claude Paroz, 3 years ago

I'm not so sure that MemoryError is only triggered by read(), but let's see how it goes and if the issue happens again in the future.

Note: See TracTickets for help on using tickets.
Back to Top