Skip to content

rtos: Fix MemoryPool and Queue destructor #4601

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

Merged
merged 2 commits into from
Jun 29, 2017

Conversation

pan-
Copy link
Member

@pan- pan- commented Jun 21, 2017

Description

Destructors of MemoryPool and Queue were not defined leaving a resource leak after destruction of any instance of this kind of objects.

This PR adds a destructor for these types which correctly release the resources. As a side effect it also fix the default destructor of the Mail class.

Status

READY

Migrations

NO

Todos

  • Review

@pan- pan- requested review from bulislaw and 0xc0170 June 21, 2017 10:26
Copy link
Member

@bulislaw bulislaw left a comment

Choose a reason for hiding this comment

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

Good catch, thanks!

Copy link
Contributor

@geky geky left a comment

Choose a reason for hiding this comment

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

Yay! Nice fix
should finish up #4492

@studavekar
Copy link
Contributor

/morph test

@mbed-bot
Copy link

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 602

Test failed!

@theotherjimmy
Copy link
Contributor

@studavekar Was this CI failure related to this PR?

@studavekar
Copy link
Contributor

Looks like tests failed logs have not been uploaded to public server, Not exactly sure about the failure.
As I re-collect timing tests failed for this PR which has dependent on load on host machine.

re-trigger the tests
/morph test

@mbed-bot
Copy link

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 681

Test failed!

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 29, 2017

/morph test

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 683

All builds and test passed!

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

Successfully merging this pull request may close these issues.

7 participants