Screenshot and debug logs are present at https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cros/917534/?debugUI=CLOUD

Thanks Sridhar for reporting this issue.

Can you check if daisy_spring, and daisy(snow) have same issue?

Able to reproduce this issue on Daisy and Daisy_Spring.

adlr can you help triage this?  Really RBS and owner?

Assign it to me. If it is a regression on the daisy boards it is preventing
the primary printing method for the milestone.

On Mon, Jan 7, 2019, 9:18 AM djmm via monorail <
monorail+v2.3908432398@chromium.org wrote:

Not able to reproduce this issue on M71 11151.100.0 Stable build.

I'm not seeing any mdns printers using daisy.

Can we verify if this is specific to daisy boards?

Yes, this is specific to daisy, daisy-skate, and daiy-spring on M72 build. M71 build does not show this issue for these three boards.

I think I know what's wrong.  Fix is in progress.

Can verify that code crashes when attempting to construct the socket on celes.

[----------] 1 test from MDnsSocketTest
[ RUN      ] MDnsSocketTest.CreateSocket
[15279:15279:0109/170906.497336:84761497343:WARNING:net_errors_posix.cc(124)] Unknown error Protocol not available (92) mapped to net::ERR_FAILED
Received signal 11 SEGV_MAPERR 000000000000
#0 0x7f7226d51d7f base::debug::StackTrace::StackTrace()
#1 0x7f7226d51901 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x7f7223882ab0 <unknown>
#3 0x7f722612a869 net::MDnsSocketTest_CreateSocket_Test::TestBody()
#4 0x7f72261d1d91 testing::Test::Run()
#5 0x7f72261d2a6f testing::TestInfo::Run()
#6 0x7f72261d2fb7 testing::TestCase::Run()
#7 0x7f72261dff97 testing::internal::UnitTestImpl::RunAllTests()
#8 0x7f72261dfafa testing::UnitTest::Run()
#9 0x7f7226fca39d base::TestSuite::Run()
#10 0x7f7226fcda50 base::(anonymous namespace)::LaunchUnitTestsInternal()
#11 0x7f7226fcd8e7 base::LaunchUnitTests()
#12 0x7f722552e9ac main
#13 0x7f7222e72a94 __libc_start_main
#14 0x7f722466302a _start
  r8: 0000000000000000  r9: 00007f7222d2f7c0 r10: 4e5241573a333433 r11: 0000000000000000
 r12: 0000222b361f35e0 r13: 0000222b353dc000 r14: 0000222b35059e00 r15: 0000222b361f35e0
  di: 0000000000000000  si: 000000000000001d  bp: 00007ffe4c5ce950  bx: 00007ffe4c5ce8f0
  dx: 00000000000001f5  ax: 00007ffe4c5ce8e8  cx: 23064966fed05e00  sp: 00007ffe4c5ce8e0
  ip: 00007f722612a869 efl: 0000000000010202 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

celes is running kernel 3.8.11

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2e49c94c24c1d93fe54b9549c9605b45e41cb8d7

commit 2e49c94c24c1d93fe54b9549c9605b45e41cb8d7
Author: Sean Kau <skau@chromium.org>
Date: Thu Jan 10 23:49:45 2019

Unbreak mDNS on older kernels

setsockopt was failing on some older kernels where the desired
option is not available.  Check errno for the unsupported error instead
of the return value which is always -1 if there is an error.

Bug:  917534 

Change-Id: Ie62cccdeab9ae2017ab1b5bf121825f97c1ccb2c
Reviewed-on: https://chromium-review.googlesource.com/c/1403090
Commit-Queue: Sean Kau <skau@chromium.org>
Reviewed-by: Eric Orth <ericorth@chromium.org>
Cr-Commit-Position: refs/heads/master@{#621804}
[modify] https://crrev.com/2e49c94c24c1d93fe54b9549c9605b45e41cb8d7/net/dns/mdns_client_unittest.cc
[modify] https://crrev.com/2e49c94c24c1d93fe54b9549c9605b45e41cb8d7/net/socket/udp_socket_posix.cc

This bug requires manual review: M72 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: govind@(Android), kariahda@(iOS), djmm@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Here's a summary of the rules that were executed: 
 - OnlyMergeApprovedChange: Rule Failed -- Revision 2e5ac42bd4339a8988cb1efa6b25eeaebbfec0d6 was merged to refs/branch-heads/3626 branch with no merge approval from a TPM! 
Please explain why this change was merged to the branch!
 - AcknowledgeMerge: Notification Required -- 

The following revision refers to this bug: 
https://chromium.googlesource.com/chromium/src.git/+/2e5ac42bd4339a8988cb1efa6b25eeaebbfec0d6

Commit: 2e5ac42bd4339a8988cb1efa6b25eeaebbfec0d6
Author: skau@chromium.org
Commiter: skau@chromium.org
Date: 2019-01-14 20:41:22 +0000 UTC

Unbreak mDNS on older kernels

setsockopt was failing on some older kernels where the desired
option is not available.  Check errno for the unsupported error instead
of the return value which is always -1 if there is an error.

Bug:  917534 

Change-Id: Ie62cccdeab9ae2017ab1b5bf121825f97c1ccb2c
Reviewed-on: https://chromium-review.googlesource.com/c/1403090
Commit-Queue: Sean Kau <skau@chromium.org>
Reviewed-by: Eric Orth <ericorth@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#621804}(cherry picked from commit 2e49c94c24c1d93fe54b9549c9605b45e41cb8d7)
Reviewed-on: https://chromium-review.googlesource.com/c/1409726
Reviewed-by: Sean Kau <skau@chromium.org>
Cr-Commit-Position: refs/branch-heads/3626@{#676}
Cr-Branched-From: d897fb137fbaaa9355c0c93124cc048824eb1e65-refs/heads/master@{#612437}

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2e5ac42bd4339a8988cb1efa6b25eeaebbfec0d6

commit 2e5ac42bd4339a8988cb1efa6b25eeaebbfec0d6
Author: Sean Kau <skau@chromium.org>
Date: Mon Jan 14 20:41:22 2019

Unbreak mDNS on older kernels

setsockopt was failing on some older kernels where the desired
option is not available.  Check errno for the unsupported error instead
of the return value which is always -1 if there is an error.

Bug:  917534 

Change-Id: Ie62cccdeab9ae2017ab1b5bf121825f97c1ccb2c
Reviewed-on: https://chromium-review.googlesource.com/c/1403090
Commit-Queue: Sean Kau <skau@chromium.org>
Reviewed-by: Eric Orth <ericorth@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#621804}(cherry picked from commit 2e49c94c24c1d93fe54b9549c9605b45e41cb8d7)
Reviewed-on: https://chromium-review.googlesource.com/c/1409726
Reviewed-by: Sean Kau <skau@chromium.org>
Cr-Commit-Position: refs/branch-heads/3626@{#676}
Cr-Branched-From: d897fb137fbaaa9355c0c93124cc048824eb1e65-refs/heads/master@{#612437}
[modify] https://crrev.com/2e5ac42bd4339a8988cb1efa6b25eeaebbfec0d6/net/dns/mdns_client_unittest.cc
[modify] https://crrev.com/2e5ac42bd4339a8988cb1efa6b25eeaebbfec0d6/net/socket/udp_socket_posix.cc

TPMs, I believe this was merged correctly.  I think your bot has a bug.

Tested on  M73_11584.0.0 build.
Tested DUT: Daisy

Browser crashing after selecting wifi printer from print dialog.
crash report link:https://crash.corp.google.com/browse?stbtiq=b891b4b31cb27037


Logs are present at https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cros/917534/new/

Can you log that as a separate bug?  That's unrelated to the wifi printing issue.

Filed new issue  crbug.com/922082 

Verification pending  issue 922082 

Verified on build M72 11316.82.0 build.
Wifi printing is working fine on Daisy.