tickets: 8288
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8288 | 2008-08-13 16:06:47 | 2011-09-28 16:12:17 | 2022-03-06 03:41:51.454952 | Accepted | closed | Database layer (models, ORM) | 1.0-alpha | worksforme | Field lookup of __gt and __gte on DecimalField causes memory blowup | 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. | nobody | odonian | 0 | 0 | 0 | 0 | 0 | 0 |