[Owfs-developers] memleak in owserver

Hi, this is very vague and unconfirmed as I can only test remote on one live-system but I suspect there is a serious memleak in owserver with (only!) Datanab-sensors *or* DS2406 (both not used in my testbed).. In use: 2.8p14/p15 I'll do further tests the next days, maybe its already fixed (then j

Re: [Owfs-developers] memleak in owserver

12:25 PM > To: owfs-developers@lists.sourceforge.net > Subject: Re: [Owfs-developers] memleak in owserver > > Further testing shows no more memory leaks (at least for my > setup and workload). Can you try the CVS version to confirm? > > Paul Alfille > > > On Thu, May

Re: [Owfs-developers] memleak in owserver

Further testing shows no more memory leaks (at least for my setup and workload). Can you try the CVS version to confirm? Paul Alfille On Thu, May 28, 2009 at 6:34 AM, Paul Alfille wrote: > The log was very helpful. I found a memory leak. I'll analyze further to > make sure that there aren't any

Re: [Owfs-developers] memleak in owserver

I submitted the request 2 years ago. I had a response asking for more information, but it hasn't moved since then. Paul Alfille On Thu, May 28, 2009 at 8:02 AM, Matthias Urlichs wrote: > Hi, > > Steinar Midtskogen: > > Has it been considered to get owfs into the Coverity scan? > > http://www.sca

Re: [Owfs-developers] memleak in owserver

Hi, Steinar Midtskogen: > Has it been considered to get owfs into the Coverity scan? > http://www.scan.coverity.com/ > That's a very good idea. To do so, the project lead should send email to: scan-ad...@coverity.com They seem to want code archive location, affirmation that the project is gover

Re: [Owfs-developers] memleak in owserver

"Michael Markstaller" writes: > I think since polling owserver more heavily (uncached dir every 500ms) it > shows a memleak. > As experience with debugging such things is close to zero, if someone can > point me to the nescessary steps, I'd be happy to create some debug-output.. > (use valgrind

Re: [Owfs-developers] memleak in owserver

vn > this morning, please let me know if I should do anything further.. > > > best regards > > Michael Markstaller > > > -Original Message- > > From: Paul Alfille [mailto:paul.alfi...@gmail.com] > > Sent: Wednesday, May 27, 2009 5:54 PM > > To: o

Re: [Owfs-developers] memleak in owserver

M > To: owfs-developers@lists.sourceforge.net > Subject: Re: [Owfs-developers] memleak in owserver > > Actually, there is a very nice thread on OWFS memory issues at: > www.mail-archive.com/owfs-developers@lists.sourceforge.net/msg > 04885.html > <http://www.mail-archive.c

Re: [Owfs-developers] memleak in owserver

Actually, there is a very nice thread on OWFS memory issues at: www.mail-archive.com/*owfs*-develop...@lists.sourceforge.net/msg04885.html Basically #defining OW_ALLOC_DEBUG and running in the foreground gives a file o

[Owfs-developers] memleak in owserver

I think since polling owserver more heavily (uncached dir every 500ms) it shows a memleak. As experience with debugging such things is close to zero, if someone can point me to the nescessary steps, I'd be happy to create some debug-output.. (use valgrind or owserver with which tracelevel?) best