{"push_id":817952963,"size":1,"distinct_size":1,"ref":"refs/heads/13.6","head":"10e790f81ad3be322193cf948e0334f9af09b00f","before":"c3521e9469f95b962e52edbbb6e0cdef6d3ceab4","commits":[{"sha":"10e790f81ad3be322193cf948e0334f9af09b00f","author":{"email":"317a993f1126881a6019d7e476a07af7fa3e05fe@digium.com","name":"Matt Jordan"},"message":"res/res_rtp_asterisk: Fix assignment after ao2 decrement\n\nWhen we decide we will no longer schedule an RTCP write, we remove the\nreference to the RTP instance, then assign -1 to the stored scheduler ID\nin case something else comes along and wants to see if anything is scheduled.\n\nThat scheduler ID is on the RTP instance. After 60a9172d7ef2 was merged to\nfix the regression introduced by 3cf0f29310, this improper assignment on a\npotentially destroyed object started getting tripped on the build agents.\n\nFrankly, this should have been crashing a lot more often earlier. I can only\nassume that the timing was changed just enough by both changes to start\nactually hitting this problem.\n\nAs it is, simply moving the assignment prior to the ao2 deference is sufficient\nto keep the RTP instance from being referenced when it is very, truly,\naboslutely dead.\n\n(Note that it is still good practice to assign -1 to the scheduler ID when we\nknow we won't be scheduling it again, as the ao2 deref *may* not always destroy\nthe ao2 object.)\n\nASTERISK-25449\n\nChange-Id: Ie6d3cb4adc7b1a6c078b1c38c19fc84cf787cda7","distinct":true,"url":"https://api.github.com/repos/asterisk/asterisk/commits/10e790f81ad3be322193cf948e0334f9af09b00f"}]}