[V8] WebKit sends unnecessary low memory notification when running memory benchmarks
https://bugs.webkit.org/show_bug.cgi?id=101474

Patch by Ulan Degenbaev <ulan@chromium.org> on 2012-11-07
Reviewed by Kentaro Hara.

Do not send low memory notification to V8 when most of memory usage
comes from V8 heap and not DOM objects. In this case V8 can schedule GC
itself more optimally.

* bindings/v8/V8GCController.cpp:
(WebCore::V8GCController::checkMemoryUsage):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@133765 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Chromium] Unreviewed gardening. Rebaseline the tests added
in http://trac.webkit.org/changeset/133686 - part deux.

* platform/chromium-win/fast/backgrounds/transformed-body-background-expected.png: Added.
* platform/chromium-win/fast/backgrounds/transformed-body-html-background-expected.png: Added.
* platform/chromium-win/fast/backgrounds/transformed-html-body-background-expected.png: Added.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@133766 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Unreviewed test expectations update.

* platform/chromium/TestExpectations:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@133767 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKitTestRunner flakily hangs when running pixel tests on Qt
https://bugs.webkit.org/show_bug.cgi?id=100686

Reviewed by Csaba Osztrogonác.

Make WebKitTestRunner harden against the situation when the coordinated
graphics rendering synchronisation fails. If we time out when waiting
for the forced repaint to finish it usually a symptom of the synchronisation
has been broken. In this case all other tests will fail with the same error.
The underlying problem is not yet known. Ths patch make us report this situation
as web process unresponsiveness, so the test harness will kill us and launch
a new instance. This will make our pixel test bot usable while it should not limit
us debugging the underlying bug.

* WebKitTestRunner/TestController.cpp:
(WTR::TestController::run):
* WebKitTestRunner/TestInvocation.cpp:
(WTR::TestInvocation::TestInvocation):
(WTR::TestInvocation::invoke):
(WTR::TestInvocation::dumpWebProcessUnresponsiveness):
(WTR::TestInvocation::didReceiveMessageFromInjectedBundle):
* WebKitTestRunner/TestInvocation.h:
(TestInvocation): Introduce new members to hold our state
that was local to invoke() so far.
* WebKitTestRunner/qt/TestInvocationQt.cpp:
(WTR::TestInvocation::dumpPixelsAndCompareWithExpected):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@133768 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Shadow] Style should update when 'pseudo' attribute is dynamically updated
https://bugs.webkit.org/show_bug.cgi?id=100918

Reviewed by Dimitri Glazkov.

Source/WebCore:

When 'pseudo' attribute is changed and its element is in ShadowTree, we enable the styleShouldRecalc flag.

It would be fast if we have a set of pseudo attribute style value in RuleFeatureSet,
but it might consume a lot of memory.

Test: fast/dom/shadow/pseudo-attribute-dynamic.html

* dom/Element.cpp:
(WebCore::Element::attributeChanged):

LayoutTests:

* fast/dom/shadow/pseudo-attribute-dynamic-expected.html: Added.
* fast/dom/shadow/pseudo-attribute-dynamic.html: Added.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@133769 268f45cc-cd09-0410-ab3c-d52691b4dbfc