Open
Bug 774756
Opened 12 years ago
Updated 2 years ago
Bubblemark is slow on mobile
Categories
(Core :: Layout, defect)
Tracking
()
NEW
People
(Reporter: jrmuizel, Unassigned)
References
Details
We spend about 5% drawing the new balls and 14% in js. The rest of the time seems to be mostly in layout.
Reporter | ||
Comment 1•12 years ago
|
||
Reporter | ||
Updated•12 years ago
|
OS: Mac OS X → Android
Hardware: x86 → ARM
Comment 2•12 years ago
|
||
CC'ing romaxa since he reported this bug before. We couldn't reproduce it because it was masked earlier by an overprinting problem.
Comment 3•12 years ago
|
||
Some of these signature are certainly caused by using making the pool thread safe:
1.7% pthread_getspecific
Other that are likely hurt by this but I'm not sure:
RgnRect::operator new
RgnRect::operator delete
RgnRectMemoryAllocator *
Comment 4•12 years ago
|
||
Another problem is that we're doing a sync transaction instead of hitting async transaction. This should only happen if we have canvas or image layers in the page.
Comment 5•12 years ago
|
||
Swift and indiscriminate back-out by ehsan for build failures:
http://hg.mozilla.org/integration/mozilla-inbound/rev/cdef000532ce
tree/layout/base/FrameLayerBuilder.cpp:2253: error: 'InvalidateThebesLayerContents' was not declared in this scope
Comment 6•12 years ago
|
||
Opps wrong bug, disregard that.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•