Closed Bug 258112 Opened 20 years ago Closed 20 years ago

Complete Mozilla Crash when attempting to access Preferences>Security>Forms> Manage Forms Data> Other Saved Information > URL Specific

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 257818

People

(Reporter: pjonescet, Unassigned)

References

Details

Attachments

(3 files)

Mozilla-bi Crash Log entry logged when crash occured
22.35 KB, application/octet-stream
Details
Pdf snapshot of Talkback log
51.74 KB, application/pdf
Details
System Crash log
22.35 KB, text/plain
Details 
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040816
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040816

In attempting to fill out all forms data in Manage Forms Data when I attempted
to access URL-Specific in "Other Saved Information" received the spining wheel
icon then an imediate Crash.

Athat point both "TalkBack" from "Mozilla" and Apple's own crash reporting
system opened. I reported first to Apple and the to Talkback same symptoms.

Reproducible: Always
Steps to Reproduce:
1.Go to Mozilla Prefences
2.Go to Privacy and Security
3.Do to Forms
4.Go to Manage Forms Data
5.Go to other Saved Information
6.Go to URL-Specific

Actual Results:  
Apple's spinning wheel of Death occured then Mozilla Crashed. Talkback openned
as well as Apple's on Crash reporting system.

Expected Results:  
It supposed to open a window or menu that indicates what information you have
saved specific to URL you have filled out forms on. I'm not sure, I've never
attempted to open iy before I tried it and this problem appeared

Setting of Mozilla Preferences
> Talkback openned

Did you send in the crash report?  If so, what's the incident ID?  If not, could
you send one in?
How does one get back to the talkback to make a copy of the log?

I did go to system console and copy and save a copy of the most recent Log entry
for Mozilla. How would I post that, or send that. Its fairly long biggest thing
is that it causes a kernel Panic when it (Mozilla) crashes

In going over the system crash log there are 5 entries in one day. there should
be that many talkback entries in the Talkback tool sent.
> How does one get back to the talkback to make a copy of the log?

Not of the log (which is not useful on its own).  Just of the incident id
number.  Run the "talkback" program; that will show the incidents and their ID
numbers.

> it causes a kernel Panic when it (Mozilla) crashes

That makes it sound like the real problem is a kernel bug and that's bringing
down Mozilla....
I've found Talback opened it and made a pdf screenshot of all the incident numbers
The last batch starting from the very bottom up to the next one with a
description are from the same type crash.

How do I post that and the Mozilla-bin crash Log to Bugzilla
> How do I post that and the Mozilla-bin crash Log to Bugzilla

Use the "Create a New Attachment" link on the bug page.
Top of Mac crash log (in private mail from reporter):

0   libgklayout.dylib   	0x0209d164
_Z14ProcessRestyleP11nsISupportsRN21nsCSSFrameConstructor11RestyleDataEPv + 0x20
1   libxpcom.dylib      	0x002ee540 PL_DHashTableEnumerate + 0x78
2   libgklayout.dylib   	0x0209d2d0
_ZN21nsCSSFrameConstructor22ProcessPendingRestylesEv + 0x60
3   libgklayout.dylib   	0x02054c84
_ZN9PresShell25FlushPendingNotificationsE12mozFlushType + 0x78
4   libgklayout.dylib   	0x0213aff8
_ZN10nsDocument25FlushPendingNotificationsE12mozFlushType + 0x1f4
5   libgklayout.dylib   	0x021b5cd8
_ZN20nsGenericHTMLElement18GetPrimaryFrameForEP10nsIContentP11nsIDocumenti + 0x48
6   libgklayout.dylib   	0x021b5d4c
_ZN20nsGenericHTMLElement22GetFormControlFrameForEP10nsIContentP11nsIDocumenti +
0x1c
7   libgklayout.dylib   	0x021d51a8 _ZN18nsHTMLInputElement5ResetEv + 0x68
8   libgklayout.dylib   	0x021d1358
_ZN18nsHTMLInputElement12AfterSetAttrEiP7nsIAtomPK9nsAStringi + 0xf8
9   libgklayout.dylib   	0x02363eec 0x2008000 + 0x35beec
10  libgklayout.dylib   	0x0224fff4
_ZN21nsXBLPrototypeBinding16AttributeChangedEP7nsIAtomiiP10nsIContentS3_i + 0x2b0
11  libgklayout.dylib   	0x0224db78
_ZN12nsXBLBinding16AttributeChangedEP7nsIAtomiii + 0x50
12  libgklayout.dylib   	0x022dd598
_ZN12nsXULElement16SetAttrAndNotifyEiP7nsIAtomS1_RK9nsAStringR11nsAttrValueiii +
0x214
13  libgklayout.dylib   	0x022dd358
_ZN12nsXULElement7SetAttrEiP7nsIAtomS1_RK9nsAStringi + 0x2c8
14  libgklayout.dylib   	0x022da600
_ZN12nsXULElement12SetAttributeERK9nsAStringS2_ + 0x94
15  libxpcom.dylib      	0x00342b58 _XPTC_InvokeByIndex + 0xd8
16  libxpconnect.dylib  	0x0063c1d4
_ZN16XPCWrappedNative10CallMethodER14XPCCallContextNS_8CallModeE + 0x9dc
17  libxpconnect.dylib  	0x00641fa8
_Z17XPC_WN_CallMethodP9JSContextP8JSObjectjPlS3_ + 0xdc
18  libmozjs.dylib      	0x0022dedc js_Invoke + 0x6cc
19  libmozjs.dylib      	0x00235874 js_Interpret + 0x6bc0
20  libmozjs.dylib      	0x0022df1c js_Invoke + 0x70c
21  libmozjs.dylib      	0x0022e128 js_InternalInvoke + 0xb8
22  libmozjs.dylib      	0x0020bf58 JS_CallFunctionValue + 0x2c
23  libgklayout.dylib   	0x0228e4d0
_ZN11nsJSContext16CallEventHandlerEP8JSObjectS1_jPlS2_ + 0x140
24  libgklayout.dylib   	0x022bdbe0
_ZN17nsJSEventListener11HandleEventEP11nsIDOMEvent + 0x440
25  libgklayout.dylib   	0x0219e14c
_ZN22nsEventListenerManager18HandleEventSubTypeEP16nsListenerStructP11nsIDOMEventP17nsIDOMEventTargetjj
+ 0x244
26  libgklayout.dylib   	0x0219e438
_ZN22nsEventListenerManager11HandleEventEP13nsPresContextP7nsEventPP11nsIDOMEventP17nsIDOMEventTargetjP13nsEventStatus
+ 0x298
27  libgklayout.dylib   	0x02292e8c
_ZN16GlobalWindowImpl14HandleDOMEventEP13nsPresContextP7nsEventPP11nsIDOMEventjP13nsEventStatus
+ 0x398
28  libgklayout.dylib   	0x02141d38 _ZN18DocumentViewerImpl12LoadCompleteEj + 0xe4

Marking dependency on bug that may fix this crash if fixed...
Depends on: 256242
Pdf snapshot of the talk back log the last entry plus the entires with no
discription just above the last entire all pertain.
Attached file System Crash log — 
The first time didn't seem to work out
The attachments occured at the same time.

Each time Mozilla Crashes I have to fill out a crash report with Apple as well
as with Mozilla Talkback. Always have.  Something about Mozilla when it crash
causes a system Kernel fault.

This is on OSX.3.5. But has done so on all versions since OSX.2.3 (first version
of OSX I used) as you can see from the Takback snapshot I haven't had many
Mozilla Crashes.

I use the Nightlies always and the one causing this crash is 1.8.a3
I can't reproduce this with my build.  Do you need to have data saved in that
section to reproduce this?

I suspect it's worth retesting this once the patch in bug 257818 lands...
I don't know hadn't been able to get into it to see if anything is entered. I
suspect so.

I've tried two builds after this (aug 16) and they don't allow downloading of
Mail, although I can send mail, and I can send and receive newspost fine. (Last
monday, and last wednesday;s version of 1.8.a.4). I didn't try to open this
preference to try simply because I had to swtich back in order to down load mail.

(I have a bug report on that as well and someone has answerred back that they
have verified the problem with no mail download exist, in X.3.5).
I just checked in some fixes that would help fix crashes of this type.  Could
someone who can reproduce this crash please retest in tomorrow's builds?
I will try Sept 13 build to see what happens.
I am trying a 1.8.a.4 Build
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a4) Gecko/20040913

But I m also using a new profile as well.

so far no crash on this bug.

But I now have a problem with no download of mail. (This is a has to do with a
bug I have reported about being unable to download mail). I will try with
regular profile and see whether information crashes the program
Just tried with my regular profile. This time didn't Crash Still no mail from
other Bug with this new build.

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a4) Gecko/20040913
The new build did appear to fix the crash for this bug. But as with others since
Aug 16th I can't download Mail. (another bug).


Almost certainly fixed by the patch in bug 257818 

*** This bug has been marked as a duplicate of 257818 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: