diff options
| author | bors-servo <metajack+bors@gmail.com> | 2015-03-16 22:21:49 -0600 |
|---|---|---|
| committer | bors-servo <metajack+bors@gmail.com> | 2015-03-16 22:21:49 -0600 |
| commit | 2281bca89252d8e37771ce2446fb5871a69903d0 (patch) | |
| tree | ba819c2ed1048d7db878d322e2d9ca82d5287418 /tests/wpt/web-platform-tests/css/css-scroll-anchoring/nested-overflow-subtree-layout.html | |
| parent | f093620922621e1877393b03968ed0ce767fdf12 (diff) | |
| parent | 2b10f6e7ea1c5a6bd6adcb5ed845c7bcb94f8e35 (diff) | |
| download | servo-2281bca89252d8e37771ce2446fb5871a69903d0.tar.gz servo-2281bca89252d8e37771ce2446fb5871a69903d0.zip | |
auto merge of #5245 : nnethercote/servo/only-one-quit-event, r=glennw
This fixes #5234, in that the huge memory spike disappears. It still takes ~15 seconds for the window to actually disappear after that first `Quit` event is received by the IOCompositor. Maybe that's a pre-existing problem.
There may be better ways to do this, like handling it on the sending side (i.e. within glutin) instead of the receiving side. I just did it this way because it seemed like the easiest thing.
Diffstat (limited to 'tests/wpt/web-platform-tests/css/css-scroll-anchoring/nested-overflow-subtree-layout.html')
0 files changed, 0 insertions, 0 deletions