Description
A generalization of TS-4444. calavera and oknet both reported crashes from trying to deallocate iobuffer readers that had already been cleared. These crashes were in 6.2.0 and 6.0.x. calavera provided a fix to null check the immediate problem reported in TS-4444. But it was generally agreed that this is probably a symptom of an iobuffer that had been freed and reallocated during the lifetime of the transaction. Filing this bug to track the broader issue.
Attachments
Issue Links
- relates to
-
TS-4444 Segfault accessing NULL connection buffer reader
-
- Closed
-