Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

7303 fix new_de_ctx disposal in case of error #11868

Closed

Conversation

zemeteri
Copy link
Contributor

@zemeteri zemeteri commented Oct 3, 2024

Make sure these boxes are checked accordingly before submitting your Pull Request -- thank you.

Contribution style:

Our Contribution agreements:

Changes (if applicable):

Link to ticket: https://redmine.openinfosecfoundation.org/issues/7303

Describe changes:

  • add DetectEngineCtxFree(new_de_ctx) call before exiting with error

Copy link

github-actions bot commented Oct 3, 2024

NOTE: This PR may contain new authors.

Copy link

codecov bot commented Oct 3, 2024

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 82.61%. Comparing base (501f79c) to head (5ff03ce).
Report is 12 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #11868      +/-   ##
==========================================
+ Coverage   82.56%   82.61%   +0.04%     
==========================================
  Files         912      912              
  Lines      249354   249356       +2     
==========================================
+ Hits       205880   205998     +118     
+ Misses      43474    43358     -116     
Flag Coverage Δ
fuzzcorpus 60.63% <0.00%> (+0.16%) ⬆️
livemode 18.72% <0.00%> (+<0.01%) ⬆️
pcap 44.08% <0.00%> (-0.01%) ⬇️
suricata-verify 62.00% <0.00%> (+<0.01%) ⬆️
unittests 58.94% <0.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Detect engine tenant reloading function hasn't got engine release call
under error label, so it is possible memory leak in case of errors in
further new detect engine initialization.

Bug: OISF#7303
@zemeteri zemeteri force-pushed the 7303-fix-mem-leak-detect-engine branch from b12a53d to 5ff03ce Compare October 4, 2024 08:13
Copy link

github-actions bot commented Oct 4, 2024

NOTE: This PR may contain new authors.

@victorjulien victorjulien added this to the 8.0 milestone Oct 8, 2024
@victorjulien
Copy link
Member

Merged in #11905, thanks!

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

Successfully merging this pull request may close these issues.

2 participants