Closed Bug 6026 Opened 25 years ago Closed 25 years ago

M5 Apprunner/Viewer die just after page begins to render.

Categories

(Core :: JavaScript Engine, defect, P3)

PowerPC
Mac System 8.5
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: cjdunn, Assigned: pierre)

References

()

Details

Running 8.5.1 on a G3/266 running Milestone 5 Release -- By "just after" I mean the header graphic and "Registration" appear for a nanosecond before it bombs. Macsbug reports: PowerPC unmapped memory exception at 619A6198. Unable to disassemble from current PC because it is a bad address. Page source shows several META tags and Javascript with a _huge_ list of countries for one entry (100+). Bug is repeatable and recoverable after "es"-ing in Macsbug (no OS problems after crash). In 1999-05-05-15-M6, same crash, but additional Macsbug info -- Bus Error at FFC76C70 _vGoDriver+00B10 while reading byte from 9D7C0350 in user data space PowerPC unmapped memory exception at 619A6198 In 1999-05-01-08, ditto (unmapped memory), ditto (Bus Error) The front page (http://setiathome.ssl.berkeley.edu) comes up fine.
Version: other
If this just turned up since may 5, it could have something to do with the introduction of xptcall support for the mac (see http://www.mozilla.org/scriptable/xptcall-faq.html ) If you remove libxptconnect from the components directory (I'm not sure what the mac equivalent is) - does it still work?
I don't believe XPConnect is installed in the components directory right now. I haven't make any build system changes to put it there.
Hm. Then I have no idea what to do with this. Any suggestions for a better owner?
Simon, can you look into this one, you Mac expert you?
Assignee: mccabe → sfraser
Assignee: sfraser → pierre
Reassigning to pierre.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I hate to do that but I'm closing it because it can no longer be reproduced with today's builds (debug + optimized) and too much time passed by since the bug was opened.
Status: RESOLVED → VERIFIED
verified, this is working with 6/15 builds
You need to log in before you can comment on or make changes to this bug.