Closed Bug 22324 Opened 26 years ago Closed 26 years ago

[PP]CreateProfileWizard crashing on [FINISH]

Categories

(Core Graveyard :: Profile: BackEnd, defect, P2)

PowerPC
Mac System 8.5
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: agracebush, Assigned: danm.moz)

References

Details

Attachments

(1 file)

Steps to reproduce: 1. Remove mozregistry, Documents folder 2. Run apprunner from icon or Mozilla Installer 3. CreateProfileWizard comes up or choose NEW in Profile Manager 4. Enter data for profile and press [FINISH] Actual Results: crash Expected results: profile created, seamonkey launch Only on Mac build 1999122108
Dan, this looks like a crash while closing a window from javascript. I think you might be the right person?
Assignee: selmer → danm
Bugzilla from Seamonkey doesn't automatically set the radio buttons. Reassigning to Dan...
*** Bug 22725 has been marked as a duplicate of this bug. ***
I have the same on 8.6. I'm desperate for a fix. Haven't been able to try out daily builds for a week now. For me, this is a showstopper. (No, I will not download a previous build to create profile resources)
*** Bug 22784 has been marked as a duplicate of this bug. ***
Severity: critical → blocker
bug 22934 prevents me from migrating a 4.x profile, this bug does not allow me to create a new profile- I am blocked
Priority: P3 → P2
Dan, are you the wrong person to own this?
I just checked in patrick beard's fix. see news://news.mozilla.org/387262C8.2B9FFB71%40netscape.com this will prevent the crash, but I imagine the real problem still needs to be fixed.
adding beard and myself to the cc list.
check bug 22725 for logs
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I can't reproduce this problem (I imagine the above-mentioned fix from Patrick Beard is to blame.) Marking fixed, credit to Patrick. I don't have any problem with Patrick's fix. He sounded worried about it, but it seems fine to me. The original coder obviously felt it was worthwhile to check whether GetContext returned a proper context, but didn't realize that it always, always returns NS_OK, necessitating a check of the returned value itself. Patrick just added that. I've fixed at least one crasher exactly the same way, and I know at least two other people who have now, too. Thumbs up from me.
Status: RESOLVED → VERIFIED
build 200011208
Component: Profile Manager → Profile Manager BackEnd
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: