[Celerity-users] memory leaks and serialize blockage
jasoninclass at googlemail.com
Fri Dec 11 03:23:26 EST 2009
You are totally right - this makes no difference - I obviously had a fantom version on celerity laying around in my vendor directory that I was testing changes on - sorry sorry.
so i re-did everything fresh and back to sqaure 1.
a. serialize and deserialize works perfectly for webclient and page when listeners have not been set.
b. since I added the browser close after click_and_attach there are no memory leaks - perfect.
the question of the day i suppose is, what on earth is causing serialize to bombout when the listeners have been set.
On Dec 11, 2009, at 4:34 AM, doridori Jo wrote:
> are you using the latest celerity ? 1.4.0 ?
> On 12/10/09, Jari Bakken <jari.bakken at gmail.com> wrote:
>> On Thu, Dec 10, 2009 at 11:28 PM, jason franklin-stokes
>> <jasoninclass at googlemail.com> wrote:
>>> so serialize works when i take @web_client out of the initialize in
>> I'd be very surprised if that was the case. Are you sure you didn't
>> change anything else?
>> I tried making the same change and I still get:
>> org/apache/commons/lang/SerializationUtils.java:111:in `serialize':
>> java.io.NotSerializableException: org.jruby.gen.InterfaceImpl874503039
>> from org/apache/commons/lang/SerializationUtils.java:133:in `serialize'
>> from test.rb:7
>> Since the JRuby interface implementation is still being added to the
>> WebClient, that makes total sense.
>> Celerity-users mailing list
>> Celerity-users at rubyforge.org
> Celerity-users mailing list
> Celerity-users at rubyforge.org
More information about the Celerity-users