On Thursday, May 08, 2014 03:16:57 AM Dan Kennedy wrote: > On 05/08/2014 06:59 AM, Charles Samuels wrote: > > This leak cursor leak can be consistently reproduced by my test program, > > but it doesn't occur every time you create and delete the cursor. > > Hi, > > Thanks for doing this. > > I don't think the script is closing all the connections. There are > 4 "open" commands and only 1 "close". I started adding a few "close" > commands, which seemed to help, but then I got an LSM_MISUSE error > (the tester program threw an exception) indicating that I was trying > to close a connection without closing all of its cursors first.
You're right! I just noticed that I was doing something dumb while generating the trace that was causing certain closes to not be traced. > > Even so - the "8 bytes definitely lost" is suspicious. I think that > one at least might be a real leak. It's not, now that I've fixed my problem. > > I'm guessing the smaller.trace script is somehow created automatically. Yes, definitely! The larger.trace is 4.8 GiB. Thanks, Charles _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
