Closed Bug 42392 Opened 24 years ago Closed 24 years ago

Crash after creating profile in custom folder on first launch

Categories

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

Product:
Core Graveyard
Component:
Profile: BackEnd
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 43892

People

(Reporter: agracebush, Assigned: racham)

Details

(Keywords: crash) 

Steps to reproduce:

Use build 2000-06-13-08 M17 (Win only so far Linux does not crash)
start with -profilemanager option
create a profile and choose folder besides default, Users50, for profile storage
press 'start'

Actual result: crash 
 profile is created in custom folder and can be launched second time

Expected result: launch with selected profile
Adding crash keyword
Keywords: crash
Why was this a front-end bug?
Assignee: ben → putterman
Component: Profile Manager FrontEnd → Profile Manager BackEnd
I was testing bug 32808 and thought it belonged to Ben.
Sorry if I was mistaken- backend you think?
reassigning to racham.  Grace, do you have a stack trace by any chance? And, is 
this still happening?
Assignee: putterman → racham
Grace,

I don't see this happening either with latest sweetlou build (2000061908) or 
with the updated local tree I have.

I guess this must have some other component's problem happened to occur at that 
point of time. If you can confirm whether this is still happening or not, I will 
proceed further.

Another thing I have noticed is that when you select a profile directory of your 
choice, the profile manager UI used to display the complete path you have 
selected. Now, you don't see anything. Is there a bug on this ? 


Grace, 

I am closing this bug as worksforme.
Please reopen if you can reproduce the behavior.

bhuvan
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Yes, I noticed this yesterday- will verify on todays build- 
I updated bug 34071 with the path not being displayed in UI- that is a bug on 
not being able to create a custom folder- should it be separate bug?
I am seeing this again on build 2000062009- tried to isolate to a particular 
drive but cannot- can reproduce at will
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Win95 - build 2000062309- error in msvcrt.dll (version 6.00.8168.00)
I'm not seeing this crash either with this morning's build 6/25/2000.  I saw the
empty directory when choosing something besides the default, but I didn't crash.
 Grace, do you have a talkback stack? I noticed that you mentioned Win95.  Does
this happen to you on NT? That might be the problem since I'm using NT. If this
is reproducible I think we'd want to fix this for beta2, so nominating.
Keywords: nsbeta2
This does happen on NT and at the point where it happens I get a dr.watson log 
and not a talkback trace.  Would that be of help?
As you are not getting talkback report.....we need to find machine where we can 
reproduce this problem. I can try reproducing this on Sean Su's win98 box and 
let us see what happens...?
Grace, 

I filed bug 43892 for the crahser that is occuring in the filepicker. That is 
what we have seen as we tried to reproduce...Marking this bug as dup of 43892.
I got the crahser on all windows machines (98, NT, 2000).

bhuvan
 

*** This bug has been marked as a duplicate of 43892 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
marking duplicate (also not crashing anymore-so other bug is fixed)
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.