It is not a security issue in itself; however, if there is a cross site or similar security problem in the browser, a separate process solve the problem. I shutdown and make sure that the browser is terminated and then start a new browser before performing any sensitive operations to overcome this short coming.

If one wants to incur the higher cost of process startup, they should be able to do so.

Anthony G. Atkielski wrote:
CarlosRivera writes:
The other option that I would like is to spin off a separate process for
the browser.

That sort of thing is OS-specific. UNIX has a low process startup cost and processes have a simple structure, so spinning off a process costs almost nothing and is very handy sometimes. Other operating systems incur a high cost for process instantiation and may not work well with this architecture. So it has to be different for each OS for best performance.

In any case, that's not a security issue.
_______________________________________________
Mozilla-security mailing list
Mozilla-security@mozilla.org
http://mail.mozilla.org/listinfo/mozilla-security

Reply via email to