1. 22 Apr, 2008 1 commit
  2. 16 Apr, 2008 3 commits
  3. 14 Apr, 2008 1 commit
  4. 04 Apr, 2008 1 commit
  5. 30 Mar, 2008 1 commit
  6. 29 Mar, 2008 17 commits
  7. 26 Mar, 2008 1 commit
  8. 23 Mar, 2008 1 commit
  9. 22 Mar, 2008 1 commit
    • Pierre d'Herbemont's avatar
      objects: Send a vlc_object_kill from vlc_object_destroy() to make sure... · f0fbb2b3
      Pierre d'Herbemont authored
      objects: Send a vlc_object_kill from vlc_object_destroy() to make sure vlc_object_release() can properly free all the allocated resources when the refcount reach zero.
      
      Previously you need to send a vlc_object_kill() prior to a vlc_object_release() to get your object actually destroyed, which rendered the refcounting unusuable in some cases.
      f0fbb2b3
  10. 19 Mar, 2008 1 commit
  11. 18 Mar, 2008 2 commits
  12. 16 Mar, 2008 1 commit
  13. 12 Mar, 2008 1 commit
  14. 03 Mar, 2008 2 commits
  15. 27 Feb, 2008 3 commits
  16. 26 Feb, 2008 2 commits
    • Pierre d'Herbemont's avatar
      d1d0a622
    • Pierre d'Herbemont's avatar
      misc/objects.c: Don't rely on vlc_object_destroy() to destroy objects, but... · a78e273e
      Pierre d'Herbemont authored
      misc/objects.c: Don't rely on vlc_object_destroy() to destroy objects, but expects vlc_object_release to do it when the refcount goes to zero.
      * Meaning, that when created objects gets a refcount to 1.
      * Destroying is instantaneous and we don't have to poll for a few secondss or so to wait until the object's refcount reach 0.
      * We now track vlc_object_t's mem leaks when libvlc_global is released (Hard error for now, so they don't get unoticed)
      * We fail hard if an object is released with a refcount of 1 without being detached from its parent and its children, to make sure such cases don't go unoticed.
      (make test or make check still pass after that one. VLC is known to leak one object when no module is loaded, this must be fixed).
      
      a78e273e
  17. 25 Feb, 2008 1 commit