Closed Bug 12815 Opened 25 years ago Closed 25 years ago

Can't start app - string error in profile

Categories

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

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

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: phil, Assigned: selmer)

Details

When I try to start the app, I die with a heap corruption. Looks like a string
is being deleted twice: once explicitly and once from nsOutputStringStream.
Here's the stack trace:

operator delete(void * 0x00a472b0) line 47 + 81 bytes
CharImpl::~CharImpl() line 215 + 20 bytes
CharImpl::`scalar deleting destructor'(unsigned int 0x00000001) + 15 bytes
BasicStringImpl::Release(BasicStringImpl * const 0x00a473e0) line 319 + 98 bytes
nsCOMPtr<nsIRandomAccessStore>::~nsCOMPtr<nsIRandomAccessStore>() line 458
nsRandomAccessStoreClient::~nsRandomAccessStoreClient() line 357 + 27 bytes
nsRandomAccessOutputStream::~nsRandomAccessOutputStream() + 49 bytes
nsOutputStringStream::~nsOutputStringStream() + 15 bytes
nsProfile::UpdateMozProfileRegistry(nsProfile * const 0x00a461e0) line 1913 + 9
bytes
nsProfile::MigrateProfileInfo(nsProfile * const 0x00a461e0) line 1828
main1(int 0x00000002, char * * 0x00a216d0) line 418
main(int 0x00000002, char * * 0x00a216d0) line 832 + 13 bytes
mainCRTStartup() line 338 + 17 bytes
KERNEL32! 77f1ba06()
I'm running with -installer, by the way
Severity: blocker → critical
Since there's a workaround (don't run with -installer) I downgraded the severity
from blocker to critical.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fixed the double delete problem. It should work ok now.
Status: RESOLVED → VERIFIED
build for 19990909
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.