old states linger in persistent object cache
Bug #487243 reported by
Marius Gedminas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ZODB Browser |
Fix Released
|
Critical
|
Marius Gedminas |
Bug Description
Take a really old Data.fs, go to root folder, look at it, go somewhere else. You get a crash:
ComponentLook
because the root folder with its old state of the root folder lingers in the ZODB object cache, and we call __setstate__ indiscriminantly in our listHistory views.
zodbbrowser should take care to restore all objects to pristine condition after calling __setstate__.
This may have even more sinister consequences: the old state might get modified and written back to the DB. I bet this explains one very curious error I've seen.
Related branches
Changed in zodbbrowser: | |
importance: | Undecided → Critical |
Changed in zodbbrowser: | |
milestone: | none → 0.5.1 |
Changed in zodbbrowser: | |
milestone: | 0.5.1 → 0.7.1 |
assignee: | nobody → Marius Gedminas (mgedmin) |
Changed in zodbbrowser: | |
status: | Confirmed → Fix Committed |
Changed in zodbbrowser: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in 0.5.1.