dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.2.5
_whitelogger has joined #cinch
Dwarf has quit [Ping timeout: 256 seconds]
Dwarf has joined #cinch
sarkyniin has quit [Ping timeout: 256 seconds]
hodI is now known as oaavl
oaavl is now known as bosma
sarkyniin has joined #cinch
britneywright has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
britneywright has joined #cinch
djbkd has quit [Quit: My people need me...]
britneywright has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sarkyniin has quit [Quit: Quit]
djbkd has joined #cinch
postmodern has quit [Quit: Leaving]
dominikh has quit [Ping timeout: 250 seconds]
dominikh has joined #cinch
_whitelogger has joined #cinch
djbkd has quit [Quit: My people need me...]
Azure has quit [Read error: Connection reset by peer]
Azure has joined #cinch
_whitelogger has joined #cinch
sarkyniin has joined #cinch
_whitelogger has quit [Ping timeout: 252 seconds]
_whitelogger has joined #cinch
sarkyniin has quit [Ping timeout: 256 seconds]
<rikai_>
Hm, is there a best practice for finding memory leaks in cinch plugins? I'm not experienced with finding memory leaks at all really (pretty noob programmer), so i'm not sure the best way to approach things. :)