Hi,

I got a memory leak-like problem.

Here's a sample code:

obj_list = []
for i in range( 100000 ):
        obj = SomeObject( parameters ... )
        obj_list.append( obj )

for obj in obj_list:
        obj.expire()
        del obj

The memory usage grows up, even if I expire(clear) the cache, and delete
the object.

My wish is as follows:
1. When an object is created, it occupies some memory and the object
   data is stored in the RDBMS( This is the default function of
   SQLObject).
2. The object should be cached in normal usage(This is the default).
3. When I delete the object, the occupied memory is freed.
   The object data still remains in the RDBMS.

I tried a patch by Dan, which is posted at 2006-05-30 in this
mailing-list, but no change is obtained in memory usage.

I searched this mailing list and found similar problems:
        "Confused about caching" by Peter, 2006-01-24
        "Problem with circular references" by Dan, 2006-05-30
        "High memory consumption" by Brian, 2006-08-05

I found that my problem may be the problem of garbage collection on
circular references, but I cannot find the solution.

Any good idea?

(sorry my broken english.)


--
株式会社ビービット 玉越 大輝
ユーザビリティ コンサルタント
beBit,Inc. Tamakoshi Hiroki [EMAIL PROTECTED]
--------------------------------------------------------
〒105-0001 東京都港区虎ノ門1-18-1 虎ノ門10森ビル7F
TEL: 03-3509-7602 / FAX: 03-3509-7605
URL: http://www.bebit.co.jp/
--------------------------------------------------------



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss

Reply via email to