> We have upgraded from JayBird 1.5 to 1.5.3, and suddenly we
> encounter a memory-buildup.
>
> Memory will build up to aprox. 100mb while batch-updating aprox.
> 10,000 records in the same transaction.
>
> It is released again doing commit or rollback.
>
> The problem resides both in 1.5.3 and 1.5.4, whereas 1.5 performs
> flawlessly.
>
> I know this is too little information for bug-hunting, but we would
> like to know if this is a known problem ?, or even behavior as
> expected ?, before we start working on a test-case.

Do you use FBConnectionPoolDataSource? Is statement pooling enabled? If both
answers are "yes", most likely you just cache all statements used in the
system. Try setting maxStatements to 0.

If you obtain connection via DriverManager, then this most likely is a bug.
Please send at least a code snippet to see where it happens.

Thanks!
Roman