|
2010-10-11
| ||
| 18:53 | • Fixed ticket [a04e42a3]: Memory leak in sqlite3_create_collation_v2() plus 2 other changes (artifact: 8aa0d174 user: drh) | |
| 17:58 | Make sure the sqlite3_create_collation() interfaces always return an error code if they fail. Ticket [a04e42a3fcacaffa3133436]. (check-in: 6464276e user: drh tags: trunk) | |
| 17:06 | • New ticket [a04e42a3] Memory leak in sqlite3_create_collation_v2(). (artifact: b298c09f user: drh) | |
| Ticket Hash: | a04e42a3fcacaffa3133436fda957343e2be0fee | |||
| Title: | Memory leak in sqlite3_create_collation_v2() | |||
| Status: | Fixed | Type: | Code_Defect | |
| Severity: | Minor | Priority: | Immediate | |
| Subsystem: | Unknown | Resolution: | Fixed | |
| Last Modified: | 2010-10-11 18:53:54 | |||
| Version Found In: | 3.7.3 | |||
| Description: | ||||
| If an OOM error occurs during sqlite3_create_collation_v2(), the function still returns SQLITE_OK instead of returning SQLITE_NOMEM. And the destructor for the application data is not called. | ||||