On Nov 27, 2007 4:05 PM, Martin Kersten
m h wrote:
I tried running the SQLAlchemy ORM testsuite. The first time it ran for a while and then mserver segfaulted. (It also grew to using 700+Megs of memory. Am assumming this is a monetdb issue, since after
not uncommon size. A point of concern is if you use like/ltrim/rtrim.... because there we detected a leak recently. which is fixed
I'm not aware of any trimming. But I'm also seeing memory growth as I run other unit tests. I'll put it on the backburner for now.
The one show below is more serious... and we would love to be able to reproduce it using a small test. If infeasible.. then run the experiment again with 'valgrind' to detect the place where dirty memory is used, or double frees are generated.
each test the tables are usually dropped). The server now has issues. It appears to start fine:
# MonetDB server v5.2.3, based on kernel v1.20.1 # Serving database 'demo' # Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs dynamically linked # Copyright (c) 1993-2007 CWI, all rights reserved # Visit http://monetdb.cwi.nl/ for further information #warning: please don't forget to set your vault key! #(see /root/MonetDB/etc/monetdb5.conf) # Listening for connection requests on mapi:monetdb://127.0.0.1:50000/ # MonetDB/SQL module v2.20.3 loaded
When I try to connect with the command line client it complains repeatedly:
!ERROR: BUNdelete: access denied to tmp_537, aborting. !ERROR: BUNdelete: access denied to tmp_537, aborting. ....
Have attached a valgrind log using this command. Let me know if you want --leak-check=full or other options. valgrind --log-file=/tmp/monetval.log ./bin/mserver5 --dbinit="include sql;"