Hi,

During a very long transaction (a massive data update on about 100 000 different objects), even with session.clear(), I noticed that the session was consuming more and more memory.
After investigations, it seems that the problem was coming from the SessionImpl.executeAll() method which adds to the 'executions' field an Executable object. The 'executions' field
is cleared only at the end of the transaction, which seems to be related
to some data coherency issue.
Why all the executable are kept till the end of the transaction?
Is there a way to get rid of these Executable objects?

Pierre