Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
May I suggest that you post the operating system and release, and the version and release of Norton 360 that you are using. Then, kindly advise if you have read the Advisory thread of zombie, and whether you have or have not applied this workaround for whatever reason. I suspect the Firefox issue is not related to general zombies but it seems sensible to eliminate that first.
I have am using Windows XP SP3 and N360 2.3.1.4
I was wondering if any else with 360 was having this problem. If not, maybe it's something else. It does seem to be an intermittent problem.
I'm guessing it's n360 just because other firefox users seems genuinely puzzled by what's going on.
I'm sorry it is not clear to me. Have you applied the zombie workaround?
This is a known issue with FF3. The firefox.exe process seems to keep running for a while after you close FF. Eventually it terminates itself. If you close FF then try to open it again straight away, it tells you the process is still running. But then, if you try a second time straight away, it will open up. I don't think this is related to Norton. You may like to refer to this thread I just posted about possible work arounds to issues such as this here.