WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WONTFIX
51335
[Qt][WK2] MappedMemoryPool is unbounded
https://bugs.webkit.org/show_bug.cgi?id=51335
Summary
[Qt][WK2] MappedMemoryPool is unbounded
Balazs Kelemen
Reported
2010-12-20 08:09:03 PST
The pool of mapped memory areas used by UpdateChunk's never release memory. This means when you resize the window to a bigger size n times we are using n piece of big area while typically one medium size would be enough for updates.
Attachments
Patch
(15.80 KB, patch)
2010-12-20 08:58 PST
,
Balazs Kelemen
no flags
Details
Formatted Diff
Diff
Patch
(15.50 KB, patch)
2010-12-20 15:15 PST
,
Balazs Kelemen
no flags
Details
Formatted Diff
Diff
Patch
(14.33 KB, patch)
2011-01-05 05:16 PST
,
Balazs Kelemen
no flags
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
Balazs Kelemen
Comment 1
2010-12-20 08:58:35 PST
Created
attachment 77009
[details]
Patch
Balazs Kelemen
Comment 2
2010-12-20 15:15:34 PST
Created
attachment 77042
[details]
Patch Eliminated the pointless base class, otherwise the same as the last one.
Balazs Kelemen
Comment 3
2011-01-03 10:41:46 PST
Comment on
attachment 77042
[details]
Patch First need to solve #51474 to avoid conflicts.
Balazs Kelemen
Comment 4
2011-01-05 05:16:57 PST
Created
attachment 77989
[details]
Patch
Kimmo Kinnunen
Comment 5
2011-01-05 23:04:38 PST
This addresses a quite serious problem with MemoryMappedPool, good. However I'm not really convinced that anybody should spend that much time polishing current MemoryMappedPool before it really is working well. To me, this patch just adds complexity on top of simple implementation. To me, address space running out is the least of the worries for MemoryMappedPool. The simple implementation was initially done just to get WK2 on Qt working -- it is not meant as end-all design. I opened another bug that discusses current problems:
https://bugs.webkit.org/show_bug.cgi?id=51984
Some of the problems are amplified by this patch. At least: - this patch adds even more calls that don't check errors (file opens, mmaps) - this patch adds polish (enums instead of bools) to the isFree flag, which is incorrect anyway
Balazs Kelemen
Comment 6
2011-01-19 08:25:31 PST
Comment on
attachment 77989
[details]
Patch We should make a consensus about do we really need the pooling optimization. Postpone this work until it has been done.
Kimmo Kinnunen
Comment 7
2011-01-19 10:41:25 PST
(In reply to
comment #6
)
> (From update of
attachment 77989
[details]
) > We should make a consensus about do > we really need the pooling > optimization. Postpone this work until > it has been done.
Or, I can add that pooling if it makes you happy. Should I do that and do another patch?
Balazs Kelemen
Comment 8
2011-01-19 14:21:50 PST
(In reply to
comment #7
)
> (In reply to
comment #6
) > > (From update of
attachment 77989
[details]
[details]) > > We should make a consensus about do > > we really need the pooling > > optimization. Postpone this work until > > it has been done. > > Or, I can add that pooling if it makes you happy. Should I do that and do another patch?
It's not about my happiness. If your experiences (benchmarks, profiling, user experience on device, etc.) does not justify the value of the optimization then it should be removed. We can reintroduce it in the future if mmap will be a bottleneck.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug