Open Bug 774756 Opened 12 years ago Updated 2 years ago

Bubblemark is slow on mobile

Categories

(Core :: Layout, defect)

ARM
Android
defect

Tracking

()

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.
OS: Mac OS X → Android
Hardware: x86 → ARM
CC'ing romaxa since he reported this bug before. We couldn't reproduce it because it was masked earlier by an overprinting problem.
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 *
Blocks: 703317
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.
Depends on: 773100
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
Opps wrong bug, disregard that.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.