Closed Bug 54338 Opened 25 years ago Closed 19 years ago

[out] and [inout] parametrs should be dealocated

Categories

(Core Graveyard :: Java to XPCOM Bridge, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: arthur.barrett, Assigned: blackconnect)

References

Details

Attachments

(2 files)

From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt) BuildID: 2000091312 Start mozilla (with blackconnect) and it brings up the assertion after: --[java]Utilities.callMethod 0 --[c++] jni Java_org_mozilla_xpcom_Utilities_callMethodByIndex 0 --[c++]bcXPCOMStub paramCount 2 Reproducible: Always Steps to Reproduce: 1.start mozilla.exe 2. 3. Actual Results: --[java]Utilities.callMethod 0 --[c++] jni Java_org_mozilla_xpcom_Utilities_callMethodByIndex 0 --[c++]bcXPCOMStub paramCount 2 Assertion is then raised Expected Results: Mozilla should start Igor suggested: to change implementation of xpAllocator::Free in bcXPCOMMarshalToolkit.cpp to virtual void Free(void *ptr) { // allocator->Free(ptr); } this seems to work
Attached file transcript
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
Changing QA contact
QA Contact: rajendra.pallath → avm
I can't reproduce this bug. Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.8.1+) Gecko/20010507
Additional info: Blackconnect source code from May 7, 2001. WinNT 4.0 with SP4.
I created bug 81122 for all memory problems closing this on as dup *** This bug has been marked as a duplicate of 81122 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Reopened. Reporter, please confirm, that this bug is still reproduced for you with latest sources.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Blocks: 81122
The real problem is that [in] and [inout] parameters passed by pointer are no dealocated. This bug happened because of preliminary fix for the described problem. That fix does not exist any more. Changing "summary" to [in] and [inout] parametrs should be dealocated
Status: REOPENED → ASSIGNED
Summary: assertion in dbgheap CrtIsValidPointer(pUserData) → [in] and [inout] parametrs should be dealocated
typo. I meant [out] and [inout] parametrs. (not "[in] and [inout]")
Summary: [in] and [inout] parametrs should be dealocated → [out] and [inout] parametrs should be dealocated
This bug has not been touched since 2001-07-05,therefore this reminder. Reporter could you please retest this with a current build and let us know if the problem is still present or the bug can be closed
Blackconnect no longer builds and hasn't been worked on since 2001. -> WONTFIX
Status: ASSIGNED → RESOLVED
Closed: 24 years ago19 years ago
Resolution: --- → WONTFIX
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: