Importing inventory pushes the OS to out-of-memory condition when many Stock Moves exist
Bug #1312045 reported by
Lionel Sausin - Initiatives/Numérigraphe
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Confirmed
|
Undecided
|
Numérigraphe | ||
OpenERP Community Backports (Addons) |
Fix Released
|
Low
|
Numérigraphe | ||
OpenERP new WMS |
New
|
Undecided
|
Unassigned |
Bug Description
Using v6.0 we're having problems importing an inventory for a location that contains >630000 Stock Moves.
The problem seems to lie in the python loop based on the browse() of the Stock Moves: it preloads too much data and pushes the OS to an out-of-memory condition (which Linux responds to by killing the openerp server).
Related branches
lp:~numerigraphe-team/ocb-addons/7.0-fill-inventory-OOM
- Laurent Mignon (Acsone) (community): Approve (code review)
- Guewen Baconnier @ Camptocamp: Approve (code review, test)
- Lionel Sausin - Initiatives/Numérigraphe (community): Abstain (co-author)
- Holger Brunn (Therp): Approve (code review)
-
Diff: 66 lines (+27/-20)1 file modifiedstock/wizard/stock_fill_inventory.py (+27/-20)
Changed in ocb-addons: | |
assignee: | nobody → Numérigraphe (numerigraphe) |
importance: | Undecided → Low |
Changed in ocb-addons: | |
status: | New → Confirmed |
Changed in openobject-addons: | |
status: | New → Confirmed |
Changed in ocb-addons: | |
assignee: | Numérigraphe (numerigraphe) → Numérigraphe (numerigraphe-team) |
summary: |
- Importing inventory pushes the OS to OOM condition when many Stock Moves - exist + Importing inventory pushes the OS to out-of-memory condition when many + Stock Moves exist |
Changed in ocb-addons: | |
status: | Confirmed → Fix Committed |
Changed in ocb-addons: | |
status: | Fix Committed → In Progress |
status: | In Progress → Fix Released |
To post a comment you must log in.
I'm rather confident there is no such problem in trunk-wms but I would love if someone from the R&D team would be so kind as to confirm it's fixed.
We have not yet tested if v7 is affected, we'll report here if it is.