Github user shinrich commented on the pull request:
https://github.com/apache/trafficserver/pull/211#issuecomment-108941270
Alan looked over this yesterday and noted that we could set the FetchSM
UserData to NULL when we free the SpdyRequest, rather than store the stream ID
and look it up on each use.
I made that change, but noticed that FetchSM is being destroyed at the same
time the SpdyRequest is freed. I think due to locking, the FetchSM isn't
really destroyed yet, so I went ahead and added the UserDataSet(NULL). In this
particular stack track it doesn't appear that the FetchSM object has been freed
yet.
So I think this change makes things better, but we still have the potential
of a rogue freed FetchSM floating around.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
