Closed Bug 2158 Opened 26 years ago Closed 26 years ago

[PP] Mac Viewer crashes upon resizing - mem partition = 1.5MB

Categories

(Core Graveyard :: Viewer App, defect, P1)

PowerPC
Mac System 8.5

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: elig, Assigned: saari)

Details

* TITLE/SUMMARY [PP] Resizing Viewer window yields immediate crash * STEPS TO REPRODUCE 0) Launch Viewer (any web page, including the default res/samples/test0.html) 1) Shrink and expand the window a single time using the resize tool (doesn't matter if you do diagonally, vertically, or horizontally.) * RESULT - What happened Immediate crash into Macsbug during the expansion. - What was expected No crash. Works fine on XPAppViewer. Will append sc and how from Macsbug. This must be a known bug, but I see no P1/P2 Macintosh bugs about crashing on resizing, so into Bugzilla it goes... * REGRESSION - Occurs On viewer (1.4.98 build) - Doesn't Occur On XPAppViewer (1.4.98 build) * CONFIGURATIONS TESTED - PowerMac 8500/150 (233 Mhz 604e), 64 MB RAM, Mac OS 8.5.1, 1024x768 (thousands of colors)
[Stack crawl/et al follows] Calling chain using A6/R1 links Back chain ISA Caller 00000000 PPC 0B514E74 03B49A40 PPC 0B50C1D8 03B499E0 PPC 0B50BBEC 03B499A0 PPC 0B77DF18 nsMacMessageSink::DispatchMenuCommand(EventRecord&, long)+004FC 03B498C0 PPC 0B77E314 nsMacMessageSink::DispatchMenuCommand(EventRecord&, long)+008F8 03B49860 PPC 0B77E6EC nsMacMessageSink::DispatchMenuCommand(EventRecord&, long)+00CD0 03B497E0 PPC 0B77E460 nsMacMessageSink::DispatchMenuCommand(EventRecord&, long)+00A44 03B49790 PPC 0B77EA30 nsMacMessageSink::DispatchMenuCommand(EventRecord&, long)+01014 03B49750 PPC 0B77DA00 nsMacMessageSink::DispatchOSEvent(EventRecord&, GrafPort*)+00040 03B49700 PPC 0B77BAC4 NS_GetWidgetNativeData(nsISupports*, void**)+0BD14 03B496A0 PPC 0B77BC2C NS_GetWidgetNativeData(nsISupports*, void**)+0BE7C 03B49660 PPC 0B77BED8 NS_GetWidgetNativeData(nsISupports*, void**)+0C128 03B49620 PPC 0B76B114 03B49590 PPC 0B76B114 03B49500 PPC 0B76B114 03B49470 PPC 0B76B09C 03B493E0 PPC 0B76B2D0 03B493A0 PPC 0B76B248 03B49350 PPC 0B521E14 NSGetFactory+02834 03B49300 PPC 0B520868 NSGetFactory+01288 03B491F0 PPC 0B51FF48 NSGetFactory+00968 03B49150 PPC 0B522760 NSGetFactory+03180 03B48F10 PPC 0B522F44 NSGetFactory+03964 03B48CD0 PPC 0B56485C NS_NewPresShell(nsIPresShell**)+020F4 03B48C70 PPC 0B64DEEC NS_NewImageDocument(nsIDocument**)+89ED0 03B48BE0 PPC 0B590A08 nsCSSProps::LookupName(const char*)+049C0 03B48B20 PPC 0B75F6F0 nsFontMetricsMac::SetFont(const nsFont&, nsIDeviceContext*)+01F5 C 03B48AE0 PPC 0B75F79C nsFontMetricsMac::SetFont(const nsFont&, nsIDeviceContext*)+0200 8 03B48A70 PPC FFD4DF6C PaintRect+0001C PowerPC unmapped memory exception at 0C03911C NQDFillCPoly+000B8
[Note: Bug does not occur on 11.4.98 debug build, as provided by Steve Dagley.]
Assignee: sdagley → saari
Related to 2198 so giving to Chris for a looksee
As of a build on the morning of 1/8/99, I could not reproduce this bug. Resizing worked fine.
This crash appears to have been specific to the low-memory situation that Pierre noted by E-mail. Using the 1/7/98 build, when I expand my screen to ~1200x1000 and resize a page, it works great with a 10 MB partition and 5 MB partition --- but the problems happens with a 1.5 MB partition. So, I'm happy for this to be marked as resolved/fixed as a result of the RAM partition increase since the build at which this was tested.
Severity: critical → major
Summary: [PP] Mac Viewer crashes upon resizing → [PP] Mac Viewer crashes upon resizing - mem partition = 1.5MB
bumping down severity to major.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
marking as fixed because of the RAM partition increase
Status: RESOLVED → VERIFIED
Verified "fixed" with 1.20.99 build, using a 4.5 MB partition (which is more likely to represent the actual memory availability of the product than the 10 MB default partition that we're currently using.)
Inserting Milestone info.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.