Skip to content

Bug async_repeat_request. Update async.c - #3916

Closed
vadimd333 wants to merge 1 commit into
OpenSIPS:3.6from
vadimd333:Fix_bug_repeat_async_request
Closed

Bug async_repeat_request. Update async.c#3916
vadimd333 wants to merge 1 commit into
OpenSIPS:3.6from
vadimd333:Fix_bug_repeat_async_request

Conversation

@vadimd333

Copy link
Copy Markdown

#3914

Summary

Details

Solution

Compatibility

Closing issues

@bogdan-iancu bogdan-iancu self-assigned this Jun 11, 2026
Comment thread modules/tm/async.c
* with data from current msg */
if ((t->uas.request) && (route_type==REQUEST_ROUTE))
if ((t->uas.request) && (route_type==REQUEST_ROUTE) &&
((msg->msg_flags & FL_TM_FAKE_REQ) == 0))

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vadimd333 , I'm not questioning the leak (and its fixing), but with this change, the transaction will not be updated from a faked request (like after a async call).
So, if you have this scenario:

  • incoming request changed (changeA) in request route
  • async jump (a first update will be done here, pushing the changeA into transaction)
  • resume in script, doing another set of changes (changeB)
  • async jump (no update here the request used in the async resume is a FAKE one)
    -> we will loose the changeB, right ?

@bogdan-iancu

Copy link
Copy Markdown
Member

This fix is not the correct one, the replacement is here d5d1760

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants