THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.

Revision history  [back]

This is a known issue, reported in Bug 16281 and fixed in Wireshark version 3.2.3. I would recommend upgrading to the latest version of Wireshark, currently version 3.2.4 as of this writing.