2203 - [PP] Closing Viewer with URL selected invokes a crash

Status: VERIFIED FIXED

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

Description

[Eli Goldberg]

* TITLE/SUMMARY
[PP] Closing Viewer with URL selected invokes a crash

* STEPS TO REPRODUCE
0) Launch Viewer
1) Select the URL, or any portion of the URL (i.e. "samples" in the default URL.)
2) Click the window's close box (or press Command-W)

* RESULT
 - What happened

Crash. Stack crawl appended.

 - What was expected

Window should gracefully close, no crash.

* REGRESSION

 - Occurs On
        viewer (1.5.98 build for Mac OS)
        viewerDebug (1.4.98 debug build for Mac OS, as copied from sdagley)

 - Doesn't Occur On
        viewer (1.5.98 build for Win32)


* CONFIGURATIONS TESTED

- PowerMac 8500/150 (233 Mhz 604e), 64 MB RAM, Mac OS 8.5.1

* MACSBUG LOG

 Calling chain using A6/R1 links
  Back chain  ISA  Caller
  00000000    PPC  0BA8533C
  03AC0040    PPC  0BA6F1A4  main+00080
  03ABFFF0    PPC  0BA6EA20  nsNativeViewerApp::Run()+00034
  03ABFFB0    PPC  0B6D613C  nsAppShell::Run()+00108
  03ABFED0    PPC  0B6D6860  nsMacMessagePump::DoMessagePump()+00194
  03ABFE70    PPC  0B91318C  LPeriodical::DevoteTimeToIdlers(const EventRecord&)+
00048
  03ABFE10    PPC  0B6BCDBC  nsTextWidget::SpendTime(const EventRecord&)+0003C
  03ABFDD0    PPC  FFD5467C  TEIdle+0001C
  03ABFCA5    PPC  0021F0CC  EmToNatEndMoveParams+00014
PowerPC unmapped memory exception at 0C032FE8 NQDGetClip+00054

Comment 1

[chris hofmann]

joe, is this a dup?

Comment 2

[Joe Francis]

At this time I don't think so, but I haven't investigated this one yet.  I
should know more tomorrow.

Comment 3

[Joe Francis]

I have reproduced this with an older build, but with new builds this no longer
occurs.

Comment 4

[Eli Goldberg]

[Will check with 1.15.99 build, and either mark as RESOLVED/FIXED or REOPENED as
appropriate. Takes place with 1.14.99 build.]

Comment 5

[Eli Goldberg]

Verified in 1.20.99 optimized build that this no longer occurs (4.5 MB memory
partition.)

I'm changing the resolution to "Resolved/Fixed", per the kooky reason that we
discussed in person.

Comment 6

[leger]

Inserting Milestone info.