OOM during some imports
Issue #404
on hold
A user reported an OOM doing an (apparently large) import.
It's possible that some recent changes have led to greatly increased memory uses in imports.
Probably worth trying something like a full Scythebill-format export and re-import, perhaps in particular re-import on top of existing data (with 100% imports). Consider also enabling observer support to force every last bit of import code to run.
Comments (2)
-
reporter
-
reporter
- changed status to on hold
Can't repro yet.
- Log in to comment
Tried this. Did not run into an OOM. Did run into problems (at least for IOC roundtripping) where duplicates are not correctly detected for one reason or another.