14974 - M9 apprunner fails to start up on B&W G3 8.6

Status: VERIFIED WORKSFORME

(SeaMonkey :: UI Design, defect, P2)

Description

[A.K.K (old account, not used anymore)]

I am running apprunner 5.0m8 from the M9 build on a Blue & White G3 with System
8.6.  This is the first time a Mozilla install was put on this system.  When the
program started, it froze while just beginning startup.  Empty menubar, mouse
movement but no interaction with other programs/windows (i.e. can't switch to
finder or another applicaiton by clicking on it's window), all other application
run fine.  Noticed that a file "Component Registry" had appeared at program
start, but no other changed on-screen.  Attempting to force-quit
(command-option-escape) froze system.  Debug switch on front of computer had no
effect.  Restarted with no apparent hard drive damage.  After search, new file
"Mozilla Registry" found with creator "MOSS" and type "REGS", but no data.

Analysis of file "Component Registry" discovered a file type and creator code
either made up of invisible characters or completely empty, according to
ResEdit.  An attempt to change the file type/creator code caused resEdit to give
an I/O error, but the changes had taken effect, according to RedEdit after the
info window was closed and then re-opened.  Contents of file:

Woodcuts.pdfRea

Comment 1

[A.K.K (old account, not used anymore)]

Attachment: "Component Registry" file

Comment 2

[A.K.K (old account, not used anymore)]

Restart of application yielded a Type 3 error, as reported by the finder, with
the Component Registry file untouched and the Mozilla Registry file deleted.

Restart of application after deleting both Mozilla and Component Registry files
yielded the freeze-up as originally described.  Force-quit not attempted.  Quit
by pressing the programmer's button and entering "PCFA700A9F4 <enter> SMFA700
<enter> G" (<enter> means press return or enter key).  This quit the program
with a Type 1 error, as reported by the Fi

Comment 3

[Sean Su]

Don, does this look like an xpapp problem or a profile manager thing?

Comment 4

[davidm]

How long did you wait before deciding the app had crashed? It can take quite a
while for the app to startup. Second does your harddrive have either a space or
a slash in it? If so try removing it, delete the moz reg and component reg and
try again. You might also try a more recent nightly build as the splash screen
will give us some more information about where it is dying.

Comment 5

[don]

David, this is yours if you want it. :-)

Comment 6

[davidm]

marking works for me. Added cmd line file to generate nspr logs

Comment 7

[A.K.K (old account, not used anymore)]

Finally managed to get the latest compile in one download.  1999101511 works for
me, as well, so it must have been a de-BinHex error or an error on an older
version.  Thanks anyway!  Now I just have the Bugzilla port to worry about!

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/67682e6f0f26
[fenix] For https://github.com/mozilla-mobile/fenix/issues/14974 - Ensure website bottom elements stay at bottom