Re: [sqlite] VFS memory leak : During lock / unlock operations

2008-02-08 Thread Florian Weimer
* Dennis Cote: > The OP said they were measuring an excess of lock calls. That would > imply that SQLite is locking files it has already locked. Is that > possible with the POSIX APIs? SQLite uses fcntl-based locks, which keep a separate lock for each byte in a file (or, more precisely, any byt

Re: [sqlite] VFS memory leak : During lock / unlock operations

2008-02-08 Thread drh
Dennis Cote <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > > > There are no lock leaks. But on the other hand, there is not > > a one-to-one mapping of lock to unlock calls. unlock is called > > more often than lock and there are often attempts to unlock files > > that have never been

Re: [sqlite] VFS memory leak : During lock / unlock operations

2008-02-08 Thread Dennis Cote
[EMAIL PROTECTED] wrote: > > There are no lock leaks. But on the other hand, there is not > a one-to-one mapping of lock to unlock calls. unlock is called > more often than lock and there are often attempts to unlock files > that have never been locked, irrc. This is harmless on windows > and u

Re: [sqlite] VFS memory leak : During lock / unlock operations

2008-02-08 Thread drh
<[EMAIL PROTECTED]> wrote: > Hi.. > >we are using sqlite3.3.4 with Integrity OS. we are facing a problem > where in the VFS memory is getting exhausted due >to large lock/unlock calls made by sqlite. Integrity support team > said that, for each file lock call made by sqlite, a definite

Re: [sqlite] VFS memory leak : During lock / unlock operations

2008-02-08 Thread drh
Brad House <[EMAIL PROTECTED]> wrote: > >> they have put traces and identified that for 1000 lock calls > >> there are only 950 unlock calls, which is a shortage of 50 unlock > >> calls. > > The os_unix.c backend to SQLite makes no attempt to match lock/unlock > > calls, because posix does not req

Re: [sqlite] VFS memory leak : During lock / unlock operations

2008-02-08 Thread Brad House
>> they have put traces and identified that for 1000 lock calls >> there are only 950 unlock calls, which is a shortage of 50 unlock >> calls. > The os_unix.c backend to SQLite makes no attempt to match lock/unlock > calls, because posix does not requires such. If you are running > on an operatin

Re: [sqlite] VFS memory leak : During lock / unlock operations

2008-02-08 Thread Sreedhar.a
: [sqlite] VFS memory leak : During lock / unlock operations <[EMAIL PROTECTED]> wrote: > Hi.. > >we are using sqlite3.3.4 with Integrity OS. we are facing a problem > where in the VFS memory is getting exhausted due >to large lock/unlock calls made by sqlite. I

Re: [sqlite] VFS memory leak : During lock / unlock operations

2008-02-07 Thread murthy.girigowda
From: Murthy Girigowda (WT01 - TES-Access Networks) Sent: Friday, February 08, 2008 12:25 PM To: 'sqlite-users@sqlite.org' Subject: VFS memory leak : During lock / unlock operations Hi.. we are using sqlite3.3.4 with Integrity OS. we are facing a problem

[sqlite] VFS memory leak : During lock / unlock operations

2008-02-07 Thread murthy.girigowda
Hi.. we are using sqlite3.3.4 with Integrity OS. we are facing a problem where in the VFS memory is getting exhausted due to large lock/unlock calls made by sqlite. Integrity support team said that, for each file lock call made by sqlite, a definite amount of memory is allocated, this