[Fedora-i18n-bugs] [Bug 626652] Memory leak

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=626652

David Zeuthen <davidz at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|dbus                        |ibus
         AssignedTo|davidz at redhat.com           |tfujiwar at redhat.com

--- Comment #6 from David Zeuthen <davidz at redhat.com> 2010-08-27 11:15:56 EDT ---
(In reply to comment #5)
> If the program in comment #4, I could see several 'definitely lost' messages
> below.
> Since there are no ibus source codes, I'll transfer to dbus.

Seriously, what kind of logic is this? Sorry but your example doesn't really
demonstrate that there is a memory leak in the D-Bus library. For starters, you
don't call dbus_shutdown() in your test program so of course it will look like
the D-Bus library is leaking.

Did you even look at the D-Bus test suite as I suggested in comment 3? If not,
then please do. In particular, please read what's in this file

 http://cgit.freedesktop.org/dbus/dbus/tree/dbus/dbus-test.c?id=dbus-1.2.24#n39

and the surrounding test suite. As you can see, the D-Bus test suite actually
checks that all allocated memory is released. Heck, it even checks the failure
paths by counting the mallocs, then running the test suite N times, failing
each malloc. With this in mind, what is more realistic? That we leak memory in
such a central function as dbus_message_new_method_call() or that, just maybe,
the user library or user application is leaking the object?

I'd really appreciate you would stop reassigning your bugs to D-Bus until it
has actually been, you know, established, that the bug is with D-Bus and not
just your code or some random example code using D-Bus. Thank you.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.