30113 2009-10-06 02:10:47 -0700 [Gtk] Adding webkit_init to the API instead of calling it inside the class_init functions 2014-04-08 18:17:39 -0700 1 1 1 Unclassified WebKit WebKitGTK 528+ (Nightly build) PC All RESOLVED INVALID P2 Normal --- 35471 1 alex webkit-unassigned christian gustavo jmalonzo mrobinson xan.lopez oldest_to_newest 152622 0 alex 2009-10-06 02:10:47 -0700 We have found some situations where doing the transparent initialization of the class_init functions is not enough, for instance when a program starts creating a KURL, the developers would have to call other function that calls the init before creating the object. This is causing problems like the one in the bug 28947, which could be in other parts of the library API. The option that could fix this problem is adding the init function to the API and asking the developers to call it before using any API function. 152629 1 alex 2009-10-06 02:27:04 -0700 (In reply to comment #0) > We have found some situations where doing the transparent initialization of the > class_init functions is not enough, for instance when a program starts creating > a KURL, the developers would have to call other function that calls the init > before creating the object. This is causing problems like the one in the bug > 28947, which could be in other parts of the library API. > Xan has pointed out in the bug 28947#3 that KURL is not a problem because it is not a public API, and the only problem is actually all the places in the library that we use that API, as always, he is right :). 156852 2 alex 2009-10-22 04:33:01 -0700 Apparently more consequences of this problem, race conditions in some situations that are causing tests to randomly fail, for instance: http://build.webkit.org/results/GTK%20Linux%2032-bit%20Debug/r49936%20(465)/storage/close-during-stress-test-stderr.txt http://build.webkit.org/results/GTK%20Linux%2032-bit%20Debug/r49936%20(465)/storage/test-authorizer-stderr.txt 158866 3 gustavo 2009-10-29 05:23:09 -0700 For the record, I am in favor of requiring that webkit_init be called, and we can, in addition to calling it where we currently do, to keep compatibility, check if it has already been called, and, if not, emit a warning saying this is deprecated. 173697 4 christian 2009-12-20 03:30:24 -0800 So this is just a problem for tests, isn't it? Or are there real use cases where an application runs into race conditions? The public objects initialize if needed as far as I'm aware. 549195 5 mrobinson 2012-02-03 15:57:57 -0800 Is this still an issue? 998971 6 mrobinson 2014-04-08 18:17:39 -0700 The GTK+ port of WebKit1 has been removed.