Closed Bug 151989 Opened 23 years ago Closed 23 years ago

Mozilla unload from memory

Categories

(Core :: XPCOM, defect)

All
OS/2
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: michele.dg, Assigned: dougt)

Details

When I start Mozilla with -turbo feature it unloads completely from memory when I close down a browser window, with a 3175 error reported by the system in xpcom.dll This is the report : 06-15-2002 11:09:10 SYS3175 PID 001d TID 0001 Slot 004f H:\MOZILLA1.0\BIN\MOZILLA.EXE c0000005 1e464117 P1=00000001 P2=00000004 P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00130760 ECX=00000056 EDX=00130760 ESI=00f04e30 EDI=0000007c DS=0053 DSACC=d0f3 DSLIM=7fffffff ES=0053 ESACC=d0f3 ESLIM=7fffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=3313 GSACC=10f3 GSLIM=00003fff CS:EIP=005b:1e464117 CSACC=d0df CSLIM=7fffffff SS:ESP=0053:00130710 SSACC=d0f3 SSLIM=7fffffff EBP=00130780 FLG=00012202 XPCOM.DLL 0001:00004117
What build were you using? Please give the build identifier from the titlebar. Plase use the Bugzilla helper when opening bugs.
Oh yes, the build I'm currently using is Mozilla 1.0 (2002060216) on OS/2 Warp 4.5 rev 14.062
Can you please try this with either a current branch build or current trunk build to see if it still happens? We can't recreate it. Thank you.
I'm currently using a 1.1a+ build (2002062808) and the problem is partially resolved. XPCOM crashes less than in past build I used.
Are you trying to restart Mozilla at all when it crashes?
Yes I tried, but now I updated to 2002070308 build and I have problems to get Mozilla -turbo loaded...it always give me a 3175 error in CHROME.DLL but could be this is another bug... Anyway, with previous build the problem was still present even when I tried to restart Mozilla.
problem(s) still existand in 1.1beta?
After our re port of nsNativeAppSupportOS2.cpp, we resolved the CHROME.DLL trap, and the XPCOM trap was fixed in a cross platform bug.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.