On 2014/03/04 22:05, Eduardo Morras wrote:
The tables have 4 rows each one, that's why I got suprised with the Out of
Memory error. The biggest row has 12KB and with the join I do, shouldn't use
more than 200KB.
Changing the ',' with the join you propose, gives Out of Memory too. It happens
on prepare phase, before binding the ? with my data. The query didn't reach the
step call.
Trying simple "SELECT r.name FROM resource AS r WHERE r.name = ?" gets "Out of
memory" too calling preparev2.
Surely something is rotten on my development platform...
Yes, something is very rotten. I would start by looking for possible memory coruptors... an array being adjusted with an index out
of the declared range, calling methods on an object via a reference that wasn't nulled after the actual object (via another ref) was
disposed. The problem with these types of errors is the thing that breaks usually have nothing to do with the thing that causes the
memory to go bad, so it is very hard to trace since we normally try to fix the thing that breaks and stares too long at the code of
the thing that broke, with which there is rarely a problem.
Do you use any memory profiling tools and checkers? It might give you some
hints.
If that query fails in an SQLite tool too, then maybe there is a problem, or if you use a custom altered version of the SQLite code.
Barring that, you need to hunt down the corrupting code - Good luck!
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
