tst_bug1349510.qml fails on trunk

Bug #1462814 reported by Chris Coulson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Fix Released
High
Chris Coulson
1.10
Won't Fix
High
Unassigned
1.11
Won't Fix
High
Unassigned
1.9
Won't Fix
High
Unassigned

Bug Description

This has started failing, possibly due to a recent change in Chromium. This looks like a "URL exceeds the max number of characters, so kill the renderer" issue.

PASS : qml-crash-test::bug1349510::initTestCase()
[0607/214012:ERROR:renderer_main.cc(200)] Running without renderer sandbox
127.0.0.1 - - [07/Jun/2015 21:40:12] "GET /empty.html HTTP/1.1" 200 -
PASS : qml-crash-test::bug1349510::test_bug1349510(row 0)
[0607/214012:ERROR:bad_message.cc(18)] Terminating renderer for bad IPC message, reason 0
[0607/214012:ERROR:bad_message.cc(18)] Terminating renderer for bad IPC message, reason 0
FAIL! : qml-crash-test::bug1349510::test_bug1349510(row 1) Uncaught exception: Message call timed out
   Loc: [/home/chr1s/src/oxide/oxide/objdir/out/imports/com/canonical/Oxide/Testing/TestUtils.js(52)]
[0607/214017:ERROR:renderer_main.cc(200)] Running without renderer sandbox
127.0.0.1 - - [07/Jun/2015 21:40:17] "GET /empty.html?foo=bar HTTP/1.1" 200 -
PASS : qml-crash-test::bug1349510::test_bug1349510(row 2)
[0607/214017:ERROR:bad_message.cc(18)] Terminating renderer for bad IPC message, reason 0
[0607/214017:ERROR:bad_message.cc(18)] Terminating renderer for bad IPC message, reason 0
FAIL! : qml-crash-test::bug1349510::test_bug1349510(row 3) Uncaught exception: Message call timed out
   Loc: [/home/chr1s/src/oxide/oxide/objdir/out/imports/com/canonical/Oxide/Testing/TestUtils.js(52)]
[0607/214022:ERROR:renderer_main.cc(200)] Running without renderer sandbox
PASS : qml-crash-test::bug1349510::test_bug1349510(row 4)
PASS : qml-crash-test::bug1349510::test_bug1349510(row 5)
PASS : qml-crash-test::bug1349510::cleanupTestCase()

Changed in oxide:
importance: Undecided → High
status: New → Triaged
milestone: none → branch-1.9
Revision history for this message
Chris Coulson (chrisccoulson) wrote :
Download full text (8.2 KiB)

Hmmm, it's not the issue I thought it was

Breakpoint 1, content::RenderProcessHostImpl::ShutdownForBadMessage (this=0x260bb00)
    at ../../../../third_party/chromium/src/content/browser/renderer_host/render_process_host_impl.cc:1054
1054 void RenderProcessHostImpl::ShutdownForBadMessage() {
(gdb) bt
#0 0x00007ffff2ffae20 in content::RenderProcessHostImpl::ShutdownForBadMessage() (this=0x260bb00)
    at ../../../../third_party/chromium/src/content/browser/renderer_host/render_process_host_impl.cc:1054
#1 0x00007ffff2eaa93f in content::(anonymous namespace)::AreURLsInPageNavigation(GURL const&, GURL const&, bool, content::RenderFrameHost*) (existing_url=..., new_url=..., renderer_says
_in_page=<optimised out>, rfh=rfh@entry=0x2610110) at ../../../../third_party/chromium/src/content/browser/frame_host/navigation_controller_impl.cc:141
#2 0x00007ffff2eaafb4 in content::NavigationControllerImpl::IsURLInPageNavigation(GURL const&, bool, content::RenderFrameHost*) const (this=<optimised out>, url=..., renderer_says_in_pa
ge=<optimised out>, rfh=rfh@entry=0x2610110) at ../../../../third_party/chromium/src/content/browser/frame_host/navigation_controller_impl.cc:1524
#3 0x00007ffff2eb6e55 in content::NavigatorImpl::DidNavigate(content::RenderFrameHostImpl*, FrameHostMsg_DidCommitProvisionalLoad_Params const&) (this=
    0xfb4910, render_frame_host=0x2610110, input_params=...) at ../../../../third_party/chromium/src/content/browser/frame_host/navigator_impl.cc:401
#4 0x00007ffff2ebc1d8 in content::RenderFrameHostImpl::OnDidCommitProvisionalLoad(IPC::Message const&) (this=this@entry=0x2610110, msg=...)
    at ../../../../third_party/chromium/src/content/browser/frame_host/render_frame_host_impl.cc:882
#5 0x00007ffff2ec3108 in content::RenderFrameHostImpl::OnMessageReceived(IPC::Message const&) (this=0x2610110, msg=...)
    at ../../../../third_party/chromium/src/content/browser/frame_host/render_frame_host_impl.cc:381
#6 0x00007ffff30018de in content::RenderProcessHostImpl::OnMessageReceived(IPC::Message const&) (this=0x260bb00, msg=...)
    at ../../../../third_party/chromium/src/content/browser/renderer_host/render_process_host_impl.cc:1552
#7 0x00007ffff39ccba0 in IPC::ChannelProxy::Context::OnDispatchMessage(IPC::Message const&) (this=0x2a372b0, message=...)
    at ../../../../third_party/chromium/src/ipc/ipc_channel_proxy.cc:294
#8 0x00007ffff2d34be1 in base::debug::TaskAnnotator::RunTask(char const*, char const*, base::PendingTask const&) (this=0x7fffffff9f08)
    at ../../../../third_party/chromium/src/base/callback.h:396
#9 0x00007ffff2d34be1 in base::debug::TaskAnnotator::RunTask(char const*, char const*, base::PendingTask const&) (this=this@entry=0xf59aa0, queue_function=queue_function@entry=0x7ffff5b
aff06 "MessageLoop::PostTask", run_function=run_function@entry=0x7ffff5baff25 "MessageLoop::RunTask", pending_task=...)
    at ../../../../third_party/chromium/src/base/debug/task_annotator.cc:62
#10 0x00007ffff2d539c4 in base::MessageLoop::RunTask(base::PendingTask const&) (this=this@entry=0xf59940, pending_task=...)
    at ../../../../third_party/chromium/src/base/message_loop/message_loop.cc:459
#11 0x00007ffff2d53ca1 in base::M...

Read more...

Changed in oxide:
milestone: branch-1.9 → branch-1.10
Changed in oxide:
milestone: branch-1.10 → branch-1.11
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Given that the original bug hasn't returned, I wonder whether the fix for this bug worked around a problem in Chromium that has since been fixed, and the test is now testing something that's not really considered valid

Changed in oxide:
milestone: branch-1.11 → branch-1.12
Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
Changed in oxide:
milestone: branch-1.12 → branch-1.13
Changed in oxide:
milestone: branch-1.13 → branch-1.14
Changed in oxide:
milestone: branch-1.14 → branch-1.15
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

I've dropped this test, and some associated code that should never be executed given that the process crashes before it gets to that point. If this was a real issue, we'd probably know about it by now

Changed in oxide:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.