Has anyone tried my solution yet?
Quick observation: After performing my workaround, I deleted FirefoxPortable. Then, when I was using Firefox, I noticed that it did not hang in memory anymore....even after opening it and closing it several times, more than enough to create a couple of zombie processes.
I tried the install of Firefox Portable and had the same results. I could open and close that application and my bookmarks would come up each time. I could even then open and close the regular Firefox version (3.0.3) and that even opened and closed a few times with bookmarks returning each time.
I went away for a couple of hours and now when I close Firefox, the process hangs and I need to end task on it or I will not get my bookmarks back.
I will have to experiment with this some more.
I am running Microsoft XP Media Center Edition, SP 3.
Yay it works. Why not export your bookmarks and import it into FirefoxPortable permanatly?
If you see my previous posts, FirefoxPortable is faster and has all the fuctionalities of Firefox. I recommand all users to make the switch to FirefoxPortable.
The suggestion of switching to portable firefox is like suggesting the way to fix the starter in my Accord is to take the Civic to work instead. 
I'm going to try the fix from other threads about "Zombie Processes" where you unregister buShell.dll. We'll see... I'm almost sure that firefox is not the only program getting "stuck"
Well FirefoxPortable has all the amenities of Firefox, so I don’t think that comparing an Accord to a Civic is an accurate description.
Sorry, my point is that it didn't solve the problem... just avoided it. I wanted the problem solved.
Unregistering the "bushell.dll" solution has gotten rid of the zombie firefox, and I think there may have been other zombie programs that are gone now.
Hi Nordberg,
I understand you want the problem resolved. As stated in my earlier message, Symantec is activly working to resolve this issue, and we will update the thread once we have the dates for the patch locked down.
-ken l
That's awesome Ken... I have found the resolution that worked for me anyway, but I'll keep an eye on this thread for the patch, so I know at that point whether or not to re-register bushell.dll
I was just pointing out that not using a program that I use everyday (even for an alternate version of the same program), was not a solution, but a kluge. Yes, I am technical enough to adjust, but I sell a multiple copies of Norton products everyday, and my non-technical customers would not consider that an acceptable solution either.
My problem is solved enough!!
Somehow applying the workaround prevents the regular Firefox from hanging in memory. For me, after applying the workaround, Firefox hung in memory once in a period of several weeks. Other users have reported the same phenomonon. Good Luck!