Closed
Bug 4051
Opened 26 years ago
Closed 25 years ago
[PP]Increasing allocated memory to >35 MB crashes on launch
Categories
(Core Graveyard :: Tracking, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
M7
People
(Reporter: cpratt, Assigned: sfraser_bugs)
Details
(Whiteboard: [RN]:M4)
Using the March 19 build, if you set the app's memory Preferred Size to 35000 K,
the app launches fine. Set it to 36000 K and the app quits at launch. (This is
using Mac OS 8.5.1 on a Rev A iMac.)
The magic numbers: 35192 - works, 35193 - crashes (as per claudius@netscape.com)
Claudius now says that although those numbers were valid for the 15 March
build, they do not appear to be valid for the 19 March build. He's currently
investigating this.
Updated•26 years ago
|
Whiteboard: is there a [] for release notes?
Comment 5•26 years ago
|
||
M7? P5? gosh, can we at least get this release noted for all the preview releases btw now and then?
This is an entirely preventable crash and lots of people crank up the mem alloc on Netscape products to as much as they can
spare, I won't comment on why that is ;-).
QA Contact: 3853 → 4137
Whiteboard: is there a [] for release notes? → [RN]:M4
Summary: Increasing allocated memory to >35 MB crashes on launch → [PP]Increasing allocated memory to >35 MB crashes on launch
This is in the M4 Release Notes, and I will confirm it stays in Release Notes of
the future until fixed. ;-)
Assignee | ||
Comment 7•25 years ago
|
||
I'm amazed that no-one has made any effort to figure out what's going on here.
ccing some more folks.
Updated•25 years ago
|
Assignee: don → pierre
Priority: P5 → P1
Comment 8•25 years ago
|
||
It happens with Viewer too. Reassigned to myself.
Updated•25 years ago
|
Assignee: pierre → sfraser
Comment 9•25 years ago
|
||
Simon has a fix. Reassigning to him.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 10•25 years ago
|
||
This is caused by a numeric overflow in the memory allocator initialization code.
The fix is pretty simple.
Comment 11•25 years ago
|
||
could you do the work to get this on the branch?
if we respin we could pick up this fix...
Assignee | ||
Comment 12•25 years ago
|
||
I guess so. What's the branch tag?
Comment 13•25 years ago
|
||
Seamonkey_M6_BRANCH
http://cvs-mirror.mozilla.org/webtools/bonsai/cvsquery.cgi?module=SeaMonkeyAll&b
ranch=Seamonkey_M6_BRANCH&branchtype=match&dir=&file=&filetype=match&who=&whotyp
e=match&sortby=Date&hours=2&date=week&mindate=&maxdate=&cvsroot=%2Fcvsroot
Assignee | ||
Comment 14•25 years ago
|
||
I checked in the fix onto the branch:
/cvsroot/mozilla/lib/mac/MacMemoryAllocator/src/nsAllocatorManager.cp,v <--
nsAllocatorManager.cp
new revision: 1.5.34.1; previous revision: 1.5
/cvsroot/mozilla/lib/mac/MacMemoryAllocator/src/nsAllocatorManager.h,v <--
nsAllocatorManager.h
new revision: 1.3.34.1; previous revision: 1.3
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 15•25 years ago
|
||
Fix checked in to trunk.
Reporter | ||
Comment 16•25 years ago
|
||
Build 1999060119, rev A iMac, Mac OS 8.6, 40 MB RAM allocated to apprunner = no
crash. Marking verified fixed.
Comment 17•25 years ago
|
||
Moving all Apprunner bugs past and present to Other component temporarily whilst
don and I set correct component. Apprunner component will be deleted/retired
shortly.
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•