Hi Denis, Hi All,
On Wed, May 9, 2018 at 1:35 AM, Denis Kudriashov <[hidden email]> wrote:
Can you tell me whether this is an application bug or possibly a bug with the Spur VMs weak collections? I'd hate for this to be an undiagnosed and unfixed VM bug.
_,,,^..^,,,_ best, Eliot |
Eliot Miranda <[hidden email]> wrote: > Can you tell me whether this is an application bug or possibly a bug with > the Spur VMs weak collections? I'd hate for this to be an undiagnosed and > unfixed VM bug. Much more likely an application bug. Copying Morphs that contain Rubric editors is non-trivial. Stephan |
2018-05-09 22:18 GMT+03:00 Stephan Eggermont <[hidden email]>:
Yes. I am sure it can't be VM issue. My candidate for leak is spotter windows history. I remember I detect some leaks when it was integrated in Pharo7. But I was not sure, it was very fast test. And it can be wrong.
|
I'm not sure if it a cause of all leaks but I realized that the method ClyDataSourceUpdateScheduler>>#processQueue that looks like this: processQueue | available next | [ available := OrderedCollection with: updateQueue next. [ next := updateQueue nextOrNil ] whileNotNil: [ available add: next ]. self runUpdateFor: available. ] repeat keeps always an indirect pointer to the full Calypso browser window because of the escaping variable (next) of the closure. Moving the temporaries definition to the inner closure fixes the leak. -- Pavel 2018-05-09 21:44 GMT+02:00 Denis Kudriashov <[hidden email]>:
|
2018-05-15 15:56 GMT+03:00 Pavel Krivanek <[hidden email]>:
Interesting. But I only see that available variable will keep instances from previous iteration, up to next update event.
|
In reply to this post by Pavel Krivanek-3
small correction, the leaking variable is "available", not "next" 2018-05-15 14:56 GMT+02:00 Pavel Krivanek <[hidden email]>:
|
Ok. I fixed found places in Calypso 2018-05-15 16:06 GMT+03:00 Pavel Krivanek <[hidden email]>:
|
Free forum by Nabble | Edit this page |