Comment 1 for bug 883775

Thanks for reporting this bug, and taking the time to make Ubuntu better! I have been able to duplicate this bug using the information you provided, and will therefore mark this bug as "confirmed".

This bug appears to be a known problem in either valgrind or glibc. If the fault lies with glibc, this would seem to indicate a trivial memory leak. There are several possible valgrind suppressions you can use to clean up its output. In my testing I found the following suppressions to be useful, although l can't claim that the set is optimal:

{
  dl_catch_error-leak-1
  Memcheck:Leak
  ...
  fun:dl_open_worker
  fun:_dl_catch_error
  ...
}
{
  dl_catch_error-leak-2
  Memcheck:Leak
  ...
  fun:_dl_close_worker
  fun:_dl_close
  fun:_dl_catch_error
  ...
}