Write a crashtest for stress-testing the WR hit-test API
Categories
(Core :: Graphics: WebRender, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox84 | --- | fixed |
People
(Reporter: kats, Assigned: kats)
References
Details
Attachments
(1 file)
Spinoff from botond's review comments on https://phabricator.services.mozilla.com/D69202
As of bug 1566599 we're calling the WR hit-test API with the FIND_ALL flag, which returns all the items at the hit-test point. There might be pathological cases where the number of results is really high. I want to write a test case that tries this out and adds appropriate limits if needed.
|
Assignee | |
Comment 1•4 years ago
|
||
I did write a test case that can make he API return large numbers of items. However it didn't seem to cause any perceptible slowdown even with hundreds of items, and instead the testcase exposed other problems (1652750). So I don't think this API will be the limiting factor when it comes to complex pages of this nature. I can put up the test later once those exposed issues are resolved.
|
|
Assignee | |
Comment 2•4 years ago
|
||
|
|
Assignee | |
Comment 3•4 years ago
|
||
Pushed by kgupta@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b095dfca878f Add a hit-testing test with a very deep stack of results. r=botond
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
Description
•