UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. start chrome
2. check for open udp ports

What is the expected behavior?
chrome should use the system's mDNS stack (avahi) if it wants to browse for (or publish) mDNS records

What went wrong?
chrome opens udp sockets on port 5353:

root:~# ss -lup src :mdns | cut -b 34-
Local Address:Port        Peer Address:Port                                                                                    
      0.0.0.0:mdns             0.0.0.0:*        users:(("chrome",pid=22621,fd=76))                                             
      0.0.0.0:mdns             0.0.0.0:*        users:(("avahi-daemon",pid=19639,fd=12))                                       
            *:mdns                   *:*        users:(("chrome",pid=22621,fd=114))                                            
         [::]:mdns                [::]:*        users:(("avahi-daemon",pid=19639,fd=13))                                       

If avahi-daemon is restarted while chrome is running, it explicitly warns about this situation:

avahi-daemon[19639]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
avahi-daemon[19639]: *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

Did this work before? N/A 

Chrome version: 68.0.3440.106  Channel: stable
OS Version: debian sid
Flash Version: Shockwave Flash 30.0 r0