With regards to comment #11 - the idea of halting an application while updating it is not unusual for daemons.
Databases, whatever.
In this case the concept is the same. There are a number of resources on the file system referenced by the application and the profile and the profile data stores that can be made inconsistent by the current system.
Comment #11 attempts to make this a Mozilla issue. It is not. It is just common sense for any large, complex, software that may reference replaced resources while running.
In fact, if this was *NOT* the case for Firefox, a prompt message to restart it would not be needed. The whole reason a prompt is needed is that as Firefox loads things that got replaced, the application starts to degrade.
This is clearly suboptimal and I'm puzzled at the pushback over this simple solution.
With regards to comment #11 - the idea of halting an application while updating it is not unusual for daemons.
Databases, whatever.
In this case the concept is the same. There are a number of resources on the file system referenced by the application and the profile and the profile data stores that can be made inconsistent by the current system.
Comment #11 attempts to make this a Mozilla issue. It is not. It is just common sense for any large, complex, software that may reference replaced resources while running.
In fact, if this was *NOT* the case for Firefox, a prompt message to restart it would not be needed. The whole reason a prompt is needed is that as Firefox loads things that got replaced, the application starts to degrade.
This is clearly suboptimal and I'm puzzled at the pushback over this simple solution.