[Webkit-unassigned] [Bug 76362] ASSERT_ICON_SYNC_THREAD fired in WebCore::IconDatabase::iconDatabaseSyncThread()

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jan 18 21:49:16 PST 2012


https://bugs.webkit.org/show_bug.cgi?id=76362





--- Comment #6 from Sriram Neelakandan <sriram.neelakandan at gmail.com>  2012-01-18 21:49:16 PST ---
I am able to hit the Assert with the following LayoutTest html

<html>
<head>
<script>
function runTest()
{
    if (window.layoutTestController) {
        layoutTestController.dumpAsText();
        layoutTestController.dumpResourceLoadCallbacks();
        layoutTestController.setIconDatabaseEnabled(true);
        var i=100;
        while (i--) {
                layoutTestController.setIconDatabaseEnabled(false);
                layoutTestController.setIconDatabaseEnabled(true);
                layoutTestController.setIconDatabaseEnabled(true);
                layoutTestController.setIconDatabaseEnabled(true);
                layoutTestController.setIconDatabaseEnabled(false);
                layoutTestController.setIconDatabaseEnabled(true);
                layoutTestController.setIconDatabaseEnabled(true);
        }
        layoutTestController.disableImageLoading();
        layoutTestController.queueReload();
    }
}
</script>
<link rel="icon" href="resources/favicon.ico" type="image/x-icon">
</head>
<body onload="runTest()">
This will test multiple IconDatabase Sync thread running
</body>
</html>

And even with this i get it just once .. on my desktop
see line number 174 in attached assert_avoided_success.txt
The ASSERT would other wise trigger (see assert_hit_fail.txt)

Now, I need some help with the LayoutTest ...

I noticed that LTC[Qt].setIconDatabaseEnabled(bool) calls WebCore::iconDatabase().open()  / WebCore::iconDatabase().close()
and hence i used the same for testing the case.

I feel that this test may become port specific.. but the actual change is port agnostic
So should we add new LTC.openIconDatabase() and LTC.closeIconDatabase() APIs for testing this case ?
Kindly Advice

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list