Possible crash if SQLiteConnection.dispose() is called from a different thread
Brought to you by:
brodybits
Menu
▾
▴
#18 Possible crash if SQLiteConnection.dispose() is called from a different thread
Delivered
nobody
None
Critical
Defect
201
2014-02-13
2010-08-21
Anonymous
No
Originally created by: ser...@gmail.com
Originally owned by: ser...@gmail.com
Access violation/segmentation fault is possible in the following scenario:
1. T1: open connection
2. T1: start any method that use sqlite3* handle
3. T1: method checks handle/state for validity, releases lock
4. T2: dispose is called, handle is now invalid
5. T1: method uses now-invalid handle - crash
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: ser...@gmail.com
(No comment was entered for this change.)
Status: Fixed
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: ser...@gmail.com
(No comment was entered for this change.)
Labels: FixVersion-201
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: ser...@gmail.com
(No comment was entered for this change.)
Status: Delivered
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: dongsh...@gmail.com
what happen to the connection when this happens? Will the connection to linger around
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: ser...@gmail.com
The behavior is not specified. It could linger. The library may take best effort to shut it down.