292338 - Mozilla 1.82 (4/28/05 built) Crash under Mac OS 10.4 (Tiger)

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Timothy Huang]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416

Mozilla 1.82 (4/28/05 built) Crash under Mac OS 10.4 (Tiger). I have 5 tabs
trying to open, but the Mozilla will quit.

Reproducible: Always

Steps to Reproduce:
1. (installed Mac OS 10.4 Tiger)
2. Open Mozilla 1.82 (4/28/05 built)
3. Crash, and Talkback agent kick in.

Actual Results:  
Mozilla quit

Expected Results:  
Fix the serious problem

Comment 1

[Timothy Huang]

If I run the Mozilla 1.77 several times (with only the Mozilla window in
Browser), then, open the latest build, the latest version of Mozilla won't
crash, with only the Mozilla window in Browser.

However, what I can not understand is this: why when ver 1.8x trying to open a
series of Tab windows, it will crash? And why ver 1.77 will only open the
Mozilla official webpage.

So as now, I have open version 1.77 till it gets the Mozilla webpage opened,
then, switch to the latest builds. Very frustrated.

It seems to me, under Mac OS Tiger, the Tab window function is not working right.

Once I successfully open the latest version, I am able to open all the Tab
windows. Very strange.

When the Mozilla crash, in the Apple's Finder "force quit" window, it will show
"no response".

Comment 2

[Timothy Huang]

I don't know if this will help. But this is what I just bumped into.

The recent Mozilla crashes were caused by trying to access a particular webpage
(http://220.132.80.74/ngh/01/INDEX.ASP).
When I remove that line in the "prefs.js" file, the Mozilla 1.8b2 (5/3/05
builds) works just fine.

I don't know why with the Tiger/1.8bx combination won't allow me to access that
particular webpage which I accessed everyday in the past.

However, after trying to download a new theme, a new line (below) was
automatically inserted into the "prefs.js" file.

user_pref("browser.startup.homepage.5", "!/!ERROR_UNDEFINED_PREF!/!");

Hope this bit will help.

Comment 3

[Frank Wein [:mcsmurf]]

Is this still a problem with a current Mozilla build? If not, i would like to
resolve it or at least lower severity.

Comment 4

[Patrick]

(In reply to comment #3)
> Is this still a problem with a current Mozilla build? If not, i would like to
> resolve it or at least lower severity.

Timothy, can you please provide feedback if this still occurs?

Comment 5

[Timothy Huang]

Hi,

please use bugzilla for all bug related correspondence. That way, all useful
information is shared by everyone.

And frankly, i have no idea to which bug report this belongs now ;)


On 6/17/05, DinoDragon <[e-mail]> wrote:

    Hello, Patrick,

    Yes, when I tried to access certain webpages, Mozilla will go into a never
ending spin or crash. Such as: http://220.132.80.74/ngh/01/index.asp

Comment 6

[Simon Fraser [no longer active]]

I'm gonna mark this INVALID unless we get a stack trace for a specific crash.

Comment 7

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 8

[Simon Fraser [no longer active]]

http://220.132.80.74/ngh/01/index.asp is dead. No info available, so closing.