Skip to content

Conversation

@jt2594838
Copy link
Contributor

When the queue of IoTConsensus is full and the queue allocation fails, the memory allocated for the whole IoTConsensus is not returned properly, resulting in memory leak.

@sonarqubecloud
Copy link

@codecov
Copy link

codecov bot commented Dec 29, 2025

Codecov Report

❌ Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 41.23%. Comparing base (80d5aea) to head (f55d6b8).
⚠️ Report is 14 commits behind head on dev/1.3.

Files with missing lines Patch % Lines
...s/iot/logdispatcher/IoTConsensusMemoryManager.java 66.66% 1 Missing ⚠️
Additional details and impacted files
@@              Coverage Diff              @@
##             dev/1.3   #16966      +/-   ##
=============================================
+ Coverage      41.12%   41.23%   +0.10%     
  Complexity       198      198              
=============================================
  Files           3589     3594       +5     
  Lines         236025   236056      +31     
  Branches       28510    28506       -4     
=============================================
+ Hits           97064    97335     +271     
+ Misses        138961   138721     -240     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jt2594838 jt2594838 merged commit 345efb7 into dev/1.3 Dec 29, 2025
21 checks passed
@jt2594838 jt2594838 deleted the fix_iot_meomory_leak_1.3 branch December 29, 2025 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants