WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
98932
[GTK] Enable IndexedDB
https://bugs.webkit.org/show_bug.cgi?id=98932
Summary
[GTK] Enable IndexedDB
Zan Dobersek
Reported
2012-10-10 11:34:29 PDT
This bug will cover enabling Indexed Database feature on the GTK port.
Attachments
Patch
(11.64 KB, patch)
2015-01-23 06:32 PST
,
Carlos Garcia Campos
zan
: review+
Details
Formatted Diff
Diff
Rebased patch
(11.51 KB, patch)
2015-05-19 06:36 PDT
,
Carlos Garcia Campos
no flags
Details
Formatted Diff
Diff
Trying again now that EWS bots have new GCC
(11.51 KB, patch)
2015-05-20 05:16 PDT
,
Carlos Garcia Campos
no flags
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
Martin Robinson
Comment 1
2012-10-28 15:41:14 PDT
***
Bug 94495
has been marked as a duplicate of this bug. ***
Carlos Garcia Campos
Comment 2
2015-01-23 06:32:22 PST
Created
attachment 245226
[details]
Patch
Carlos Garcia Campos
Comment 3
2015-01-23 08:37:49 PST
Weird build error in our EWS again, look unrelated to the patch.
Carlos Garcia Campos
Comment 4
2015-01-26 00:25:26 PST
Committed
r179107
: <
http://trac.webkit.org/changeset/179107
>
WebKit Commit Bot
Comment 5
2015-01-26 01:04:02 PST
Re-opened since this is blocked by
bug 140880
Carlos Garcia Campos
Comment 6
2015-01-26 01:28:39 PST
So, we need to either bump the minimum GCC version required or remove the AsyncTask implementation using C++ lambdas, see
bug #140881
.
Carlos Garcia Campos
Comment 7
2015-05-02 01:54:30 PDT
(In reply to
comment #6
)
> So, we need to either bump the minimum GCC version required or remove the > AsyncTask implementation using C++ lambdas, see
bug #140881
.
Maybe we can bump the GCC requirements now for the new cycle. Debian stable has 4.9.2, we should probably update our bots to jessie at some point this cycle. It's a shame this feature is blocked by a compiler bug.
Martin Robinson
Comment 8
2015-05-02 09:11:25 PDT
(In reply to
comment #7
)
> (In reply to
comment #6
) > > So, we need to either bump the minimum GCC version required or remove the > > AsyncTask implementation using C++ lambdas, see
bug #140881
. > > Maybe we can bump the GCC requirements now for the new cycle. Debian stable > has 4.9.2, we should probably update our bots to jessie at some point this > cycle. It's a shame this feature is blocked by a compiler bug.
Let's just make indexed database depend on the newer version of GCC. This should be pretty easy. It's the path of least resistance while we figure out what to do. We'll need too coordinate updating the bots.
Martin Robinson
Comment 9
2015-05-02 09:12:45 PDT
(In reply to
comment #8
)
> (In reply to
comment #7
) > > (In reply to
comment #6
) > > > So, we need to either bump the minimum GCC version required or remove the > > > AsyncTask implementation using C++ lambdas, see
bug #140881
. > > > > Maybe we can bump the GCC requirements now for the new cycle. Debian stable > > has 4.9.2, we should probably update our bots to jessie at some point this > > cycle. It's a shame this feature is blocked by a compiler bug. > > Let's just make indexed database depend on the newer version of GCC. This > should be pretty easy. It's the path of least resistance while we figure out > what to do. We'll need too coordinate updating the bots.
Note that the latest LTS version of Ubuntu only has 14.10, but we can recommend clang in that case hopefully.
Michael Catanzaro
Comment 10
2015-05-03 14:20:13 PDT
I don't mind bumping the compiler requirement, since this is a major feature and not just a code cleanup. But looking at the test expectations, is this really ready? It seems enabling IndexedDB will introduce several known crashes....
Carlos Garcia Campos
Comment 11
2015-05-18 02:24:14 PDT
(In reply to
comment #8
)
> (In reply to
comment #7
) > > (In reply to
comment #6
) > > > So, we need to either bump the minimum GCC version required or remove the > > > AsyncTask implementation using C++ lambdas, see
bug #140881
. > > > > Maybe we can bump the GCC requirements now for the new cycle. Debian stable > > has 4.9.2, we should probably update our bots to jessie at some point this > > cycle. It's a shame this feature is blocked by a compiler bug. > > Let's just make indexed database depend on the newer version of GCC. This > should be pretty easy. It's the path of least resistance while we figure out > what to do. We'll need too coordinate updating the bots.
I would not make the option depending on the compiler, we will have to upgrade the bots to test indexeddb, so we won't be testing wk build with previous versions of GCC anymore. Or if we don't upgrade the bots to ensure wk still builds with previous versions of GCC we won't be testing indexeddb.
Carlos Garcia Campos
Comment 12
2015-05-18 02:27:29 PDT
(In reply to
comment #10
)
> I don't mind bumping the compiler requirement, since this is a major feature > and not just a code cleanup. But looking at the test expectations, is this > really ready? It seems enabling IndexedDB will introduce several known > crashes....
I'll check the current status, it's early in the release cycle, we can try to fix those crashes once we have basic support landed.
Martin Robinson
Comment 13
2015-05-18 16:30:45 PDT
(In reply to
comment #11
)
> I would not make the option depending on the compiler, we will have to > upgrade the bots to test indexeddb, so we won't be testing wk build with > previous versions of GCC anymore. Or if we don't upgrade the bots to ensure > wk still builds with previous versions of GCC we won't be testing indexeddb.
Isn't untested support for a compiler better than dropping support completely?
Carlos Garcia Campos
Comment 14
2015-05-18 23:00:25 PDT
(In reply to
comment #13
)
> (In reply to
comment #11
) > > > I would not make the option depending on the compiler, we will have to > > upgrade the bots to test indexeddb, so we won't be testing wk build with > > previous versions of GCC anymore. Or if we don't upgrade the bots to ensure > > wk still builds with previous versions of GCC we won't be testing indexeddb. > > Isn't untested support for a compiler better than dropping support > completely?
I don't think so, I prefer to drop support for buggy versions of the compiler, and not making important features depend on the compiler.
Carlos Garcia Campos
Comment 15
2015-05-19 06:36:33 PDT
Created
attachment 253383
[details]
Rebased patch Fortunately build still works with indexeddb enabled. I've updated the test expectations, I got only one crash and a lot of other failures (all of them except one common to mac). run-webkit-tests --gtk storage/indexeddb http/tests/security/cross-origin-indexeddb-allowed.html http/tests/security/cross-origin-indexeddb.html http/tests/security/no-indexeddb-from-sandbox.html fast/history/page-cache-indexed-closed-db.html fast/history/page-cache-indexed-opened-db.html Found 236 tests; running 150, skipping 86. Running 4 WebKitTestRunners in parallel. All 150 tests ran as expected.
Carlos Alberto Lopez Perez
Comment 16
2015-05-20 04:24:10 PDT
(In reply to
comment #8
)
> We'll need too coordinate updating the bots.
I have just updated the 4 bots that I control: GTK Linux 64-bit Debug (Build) GTK Linux 64-bit Debug (Tests) GTK Linux 64-bit Release (Build) GTK Linux 64-bit Release (Perf) GTK Linux 64-bit Release (Tests) They are now all running Debian 8.0 with gcc-4.9.
Gustavo Noronha (kov)
Comment 17
2015-05-20 05:01:00 PDT
GCC 4.9 also available on both I maintain now =)
Carlos Garcia Campos
Comment 18
2015-05-20 05:16:38 PDT
Created
attachment 253439
[details]
Trying again now that EWS bots have new GCC
Carlos Garcia Campos
Comment 19
2015-05-25 00:05:24 PDT
Committed
r184850
: <
http://trac.webkit.org/changeset/184850
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug