Field lookup of __gt and __gte on DecimalField causes memory blowup
|Reported by:||odonian||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||1.0-alpha|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Somewhere between Django alpha 1 and 2, it seems a bug was introduced where using a field lookup of gt or gte on a DecimalField causes an instance of the development server (and probably other server instances, e.g. mod_python) to rapidly grow in memory and consume system resources (primarily memory). Perhaps a race condition is being triggered. I have to kill the dev server to get my system (running Linux) under control again.
There were no such problems seen with the exact same code in the alpha 1 svn, as far as I recall. I notice some changes have been made to the DecimalField #8143, but these are pre-existing values already in the database. I'm using the trunk at revision 8336.
Change History (5)
comment:1 Changed 8 years ago by
|Patch needs improvement:||unset|
|Triage Stage:||Unreviewed → Accepted|
|Version:||SVN → 1.0-alpha|