#2579 trace shared mem leak

Memory_Leak
pending-fixed
sfcb (1090)
7
2012-12-06
2012-12-05
No

The shared memory segment that is created for local connect clients is not released. This can result in consumption of all the available segments.

Discussion

  • Michael Chase-Salerno

    Patch adds a cleanup via an atexit() call.

     
  • Michael Chase-Salerno

    Patch committed to git master and cvs head.

    The patch cleansup the shared mem segment, but only the last one created. If a client calls newCIMCENV multiple times, it will not be able to clean them all. There shouldn't be any reason for a client to do that though.

     
  • Michael Chase-Salerno

    • status: open --> pending-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks