Closed Bug 65260 Opened 24 years ago Closed 23 years ago

PSM process is started only once per browser session

Categories

(Core Graveyard :: Security: UI, defect)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED WONTFIX

People

(Reporter: echo.choi, Assigned: javi)

Details

I've seen, but not been able formulate a procedure to reproduce, that PSM
process disappear after successfully visiting some sites. However, the current
implementation of nsPSMComponent does not restart the PSM process. As a result,
user must restart browser to visit other security sites.
I am 99% positive the reporter is right on this one. I can see how that can
cause a problem. Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Reassigning. I have not noticed this behavior. What platform do you see this on?
Assignee: ddrinan → javi
It seems like PSM crashed in the background or something.  PSM will not shutdown 
until the control connection disappears.

Until the we know what causes PSM to crash or disappear, we stand little to no 
chance of fixing this.
It's my mistake to mention two problems at the same time. What I really mean  
is that I think the psm-glue can do a better job by restarting the psm process, 
regardless of what causes psm to crash. It is the psm-glue code which start the 
psm process and establish all sort of connections in the first place, it make 
sense for it to start psm again if it is no longer available.

However, the current implementation works, if the psm process never die. And it 
is not very often that psm disappear. I have to agree that this is a low 
priority bug.

To see what I saw, try this: launch mozilla, visiting some security sites and 
wait for it to finish loading. Then, use 'killall psm' to kill all psm process. 
Then, try visit some security sites. Notice that psm process are not restarted 
and all visit to security sites fail since.
Marking wontfix. This should not be a problem now that PSM 2.0 is integrated 
into the nightly builds.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Verified.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.