running w2k_sp4, PG 3.0_beta1, and Firefox PR 1.01 (/0.10.1). I have Fx in protected zone and I notice systray icon flashing from time to time and saw related Alert log entry to Fx. the first one said that Fx denied access to physical memory. (I have 1024 mb RAM and big swap file size). so I set protect to allow Fx to access memory and then noticed that past few days that after I closed Fx onscreen, it appeared closed, and no open ports, but found Fx process still running and using about 50% cpu. I had to kill the Fx process with task manager / sysinternals process explorer 8.52. no insight from moz forum re this. but then I went back to PG protection and denied Fx access to physical memory (default?) and I have not seen this "closing_hang" since. curious why Fx wants to access physical memory, or is that common, and if so then why the apparent hang. next tonight I see PG blocked Fx from creating a global mouse hook. ok... not sure what that means or why Fx want to do that. given the above hang, I just left the PG setting as it, ie, not allowing global hooks. is it "normal" for Fx to try to take these two actions. Fx seems to run fine (better!) despite PG blocking these actions. ps. yes, I know there is a more current beta, but beta1 is rock solid here so I'm just waiting for final release; unless, some critical issue fix in current beta.