RESOLVED WONTFIX 109548
[chromium-android] WebFrameTest.ReplaceMisspelledRange crashes
https://bugs.webkit.org/show_bug.cgi?id=109548
Summary [chromium-android] WebFrameTest.ReplaceMisspelledRange crashes
jochen
Reported 2013-02-11 23:40:16 PST
Since the WebKit roll 142426:142523, WebFrameTest.ReplaceMisspelledRange crashes on Android Tests and Android Tests (dbg) Note: Google Test filter = WebFrameTest.ReplaceMisspelledRange:WebPageNewSerializeTest.SVGImageDontCrash [==========] Running 2 tests from 2 test cases. [----------] Global test environment set-up. [----------] 1 test from WebFrameTest [ RUN ] WebFrameTest.ReplaceMisspelledRange [WARNING:proxy_service.cc(887)] PAC support disabled because there is no system implementation [ CRASHED ]
Attachments
Patch (1.48 KB, patch)
2013-02-11 23:48 PST, jochen
no flags
jochen
Comment 1 2013-02-11 23:48:32 PST
jochen
Comment 2 2013-02-12 00:04:55 PST
Comment on attachment 187784 [details] Patch Clearing flags on attachment: 187784 Committed r142590: <http://trac.webkit.org/changeset/142590>
jochen
Comment 3 2013-02-12 00:05:00 PST
All reviewed patches have been landed. Closing bug.
jochen
Comment 4 2013-02-12 00:05:56 PST
reopening to track the underlying issue
Rouslan Solomakhin
Comment 5 2013-02-12 11:00:37 PST
Is there a stack trace?
Rouslan Solomakhin
Comment 7 2013-02-22 14:04:18 PST
Why is this reopened? Did disabling the test on Android not solve the problem?
jochen
Comment 8 2013-02-23 01:48:39 PST
No, it didn't solve the problem. Fixing the crash will solve the problem
Rouslan Solomakhin
Comment 9 2013-02-25 11:24:43 PST
Is this the chromium-android platform?
jochen
Comment 10 2013-02-25 11:29:20 PST
Yes, it's chromium android
John Knottenbelt
Comment 11 2013-03-18 10:16:49 PDT
It could be that this test is failing because, on Android, the data: URLs are going through the network stack instead of being mocked. See WebURLLoaderImpl::Context::CanHandleDataURL in src/webkit/glue/weburlloader_impl.cc. A fix might be to use registerMockedHttpURLLoad
Peter Beverloo
Comment 12 2013-04-08 11:10:05 PDT
Resolving as WontFix given that Chromium moved to Blink.
Note You need to log in before you can comment on or make changes to this bug.