Closed Bug 59806 Opened 25 years ago Closed 25 years ago

PSM stops responding, spikes CPU

Categories

(Core :: Security, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED DUPLICATE of bug 34834

People

(Reporter: bugzilla-mozilla-20220926, Assigned: security-bugs)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22 i686; en-US; m18) Gecko/20001108 BuildID: 2000110808 After several transactions on www.chapters.ca (adding entries to a wish list), PSM stopped responding and headed for 100% CPU usage. Mozilla reported 'connection refused'. Killing the PSM processes, then trying to navigate again in Mozilla, crashed the browser (Talkback ID TB20807011E). Reproducible: Always Steps to Reproduce: 1. Add several entries to your wish list at http://www.chapters.ca. Actual Results: After adding several entries (once after 3, once after 7 or 8), PSM spiked. (Oops, Bugzilla helper doesn't have a PSM field. Assigning to Security: General in browser, and will reassign to PSM daemon.) The Talkback trace probably isn't of much use here. If there's any way I can provide information on the PSM state, please let me know and I will.
This resembles bug 34834, now marked fixed and verified as such, with PSM 1.4. For the curiosity of it: how many psm threads were there?
On my Win98 machine, the MS process viewer reports 128 threads for PSM. Plus PSM kept hanging around even after I exited Mozilla. This is with PSM 1.3, since that's the only one I have access to (through the Install PSM menu).
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Yes, this does look a lot like 34834. It seems PSM 1.4 isn't available for download yet, though. 8^( *** This bug has been marked as a duplicate of 34834 ***
After you install PSM 1.3 from iPlanet, you can use the files below to replace the PSM 1.3 files. This is not the final version of PSM 1.4. http://www.concentric.net/~unruh/linux-psm1.4.zip http://www.concentric.net/~unruh/win-psm1.4.zip
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.