Bug #7041: Memory leak in Mutex

• Status: Closed
• Assignee: kosaki (Motohiro KOSAKI)
• Target version: -
• ruby -v: ruby 2.0.0dev (2012-09-20 trunk 36995) [x86_64-freebsd10.0]

[stass (Stanislav Sedov)]

=begin
Ruby does not destroy pthread condattr structure after allocating and using it in pthread_thread.c:native_cond_initialize().
This causes a memory leak that can be demonstrated by the following snipplet:

loop do
Mutex.new
GC.start
end

The patch attached fixes it.
This happens on both 1.9 and head.
=end

[stass (Stanislav Sedov)]

Ruby does not destroy pthread condattr structure after allocating and using it in pthread_thread.c:native_cond_initialize().
This causes a memory leak that can be demonstrated by the following snipplet:

loop do
Mutex.new
GC.start
end

The patch attaches fixes this.
The bug happens on both 1.9 and head.

[shyouhei (Shyouhei Urabe)]

• Description updated (diff)
• Category changed from core to YARV
• Status changed from Open to Assigned
• Assignee set to ko1 (Koichi Sasada)
• Priority changed from 6 to Normal

[kosaki (Motohiro KOSAKI)]

• Assignee changed from ko1 (Koichi Sasada) to kosaki (Motohiro KOSAKI)

good catch.

[kosaki (Motohiro KOSAKI)]

• Status changed from Assigned to Closed
• % Done changed from 0 to 100

This issue was solved with changeset r37001.
Stanislav, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

---

• thread_pthread.c (native_cond_initialize): destroy condattr
  after using it. Patch by Stanislav Sedov. Thank you.
  [Bug #7041] [ruby-core:47619]