Manuscript (Case [Issue]20848) FastTable - Fast table lead to memory leak in filter mode

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Manuscript (Case [Issue]20848) FastTable - Fast table lead to memory leak in filter mode

Pharo Issue Tracker
Manuscript Notification
avatar
Bug in Project:  FastTable: Misc  •  You are subscribed to this case
You are right. I found problem in Calypso panes with filter. And I did some workaround to prevent it.

Now I wonder how it works. The process runs simple #repeat loop without any condition to return. And it does not stored in any variable:

FTFilterFunction>>spawnFilterUpdateThread
    "Runs in background, thank to Henrik Johansen for this"    [ | oldPattern |
    oldPattern := nil.
    [ isEditingSemaphore wait.
    "If pattern has changed, see if we need to filter.
    If not, it's probably an extraneous signal received while we were waiting for 0.2 seconds, and we discard then till we end up waiting for filterChangeSemaphore again"
    oldPattern ~= pattern
        ifTrue: [ oldPattern := pattern.
            0.2 seconds wait.
            "Pattern still the same? If not, just loop again and end up waiting for another 0.2 secs"
            oldPattern = pattern
                ifTrue: [ self filter ] ] ] repeat ] forkAt: Processor userBackgroundPriority
Priority Priority: 3 – Must Fix Status Status: Work Needed
Assigned To Assigned to: Everyone Milestone Milestone: Pharo7.0

Go to Case
No longer need updates? Unsubscribe from this case.

Don't want Manuscript notifications anymore? Update your preferences.

Manuscript

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker