Opened 8 years ago
Closed 6 years ago
#1401 closed defect (invalid)
Rasql_Memory leak with Select into when insert with many MDDs
Reported by: | Bang Pham Huu | Owned by: | dkamov |
---|---|---|---|
Priority: | major | Milestone: | 9.7 |
Component: | rasql | Version: | development |
Keywords: | rasql memleak | Cc: | Dimitar Misev |
Complexity: | Medium |
Description
Run the attchment script to test, it will create a collection and insert a dummy data into it as first MDD, then use this query to insert over itself.
After running the query ~ 10 times, the occupied memory can show that it was leak without being released.
rasql -q 'select (char)c into test_1 from test_1 as c' --user rasadmin --passwd rasadmin
Attachments (1)
Change History (4)
by , 8 years ago
Attachment: | test_memleak_select_into.sh added |
---|
comment:1 by , 6 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:2 by , 6 years ago
Milestone: | 10.0 → 9.7 |
---|
comment:3 by , 6 years ago
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
This is not a memory leak. You're doing the select into 12 times and this is duplicating the arrays in test_1 at each iteration. At the end you have 212 arrays and this takes a bunch of memory.
Note:
See TracTickets
for help on using tickets.
@dkamov to check for the leak run this valgrind command:
valgrind —leak-check=full —track-origins=yes —tool=memcheck directql -q 'select (char)c into test_1 from test_1 as c' -d /opt/rasdaman/data/RASBASE —user rasadmin —passwd rasadmin