Closed Bug 108738 Opened 23 years ago Closed 23 years ago

calling nsCString::Replace can cause a hang

Categories

(Core :: XPCOM, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 108734

People

(Reporter: darin.moz, Assigned: scc)

Details

consider this sample program: #include "nsString.h" int main() { nsCString foo; foo.Assign("foo://www.aol.com:8989/hello/foo.html"); printf("foo=[%s]\n", foo.get()); foo.Replace(6, 11, nsDependentCString("www.yahoo.com", 13)); printf("foo=[%s]\n", foo.get()); return 0; } foo.Replace never returns.
possibly related to bug 108734
Severity: normal → critical
Figured out why this is happening. See bug 108734 for an explanation. *** This bug has been marked as a duplicate of 108734 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Dupe didn't take.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Dupe, take 2 *** This bug has been marked as a duplicate of 108734 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → DUPLICATE
Component: String → XPCOM
You need to log in before you can comment on or make changes to this bug.