Why sometimes Wireshark restarts after a profile change?
Sometimes Wireshark does not need to restart, other times it has to be restarted for a profile change to be effective. What is the hint?
What version of Wireshark are you running? Please post Wireshark's Help -> About Wireshark details. Also, what differences are there between profiles that aren't effective immediately when changing profiles?
I.e., the answer may be "because the Wireshark developers missed something in the code that handles some settings that can be changed by a profile change, so that the profile change doesn't cause an update"; if you can indicate what settings change in a profile change, but don't have that change take effect until after a restart, that would make it easier to find something we missed.
You can switch
from a profile with nameres.mac_name: TRUE to a profle with nameres.mac_name: FALSE
without restarting Wireshark. But just the first time (say when Wireshark starts by using a "TRUE" profile).
From then, every boolean change requires a restart, even from TRUE to FALSE.
I'm running
(more)