[jira] [Updated] (TS-4454) iobuffer readers are being cleared
[ https://issues.apache.org/jira/browse/TS-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-4454: --- Fix Version/s: (was: 7.0.0) 7.1.0 > iobuffer readers are being cleared > -- > > Key: TS-4454 > URL: https://issues.apache.org/jira/browse/TS-4454 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: Susan Hinrichs >Assignee: Susan Hinrichs > Fix For: 7.1.0 > > > A generalization of TS-. [~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-. 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4454) iobuffer readers are being cleared
[ https://issues.apache.org/jira/browse/TS-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4454: -- Fix Version/s: 7.0.0 > iobuffer readers are being cleared > -- > > Key: TS-4454 > URL: https://issues.apache.org/jira/browse/TS-4454 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: Susan Hinrichs >Assignee: Susan Hinrichs > Fix For: 7.0.0 > > > A generalization of TS-. [~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-. 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
