Closed Bug 93807 Opened 23 years ago Closed 23 years ago

Something about this email crashes Fizzilla

Categories

(SeaMonkey :: MailNews: Message Display, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: masri, Assigned: sspitzer)

Details

Attachments

(2 files)

Platform; PowerBook G3/300/192Mb/25Gb, MacOS X 10.0.4
Fizzilla Build: 2001073005

1) Copy & paste the attached email into your Inbox file in your Mozilla folder.

2) Launch Mozilla, go to mail.

3) Click your Inbox so Mozilla rebuilds your Inbox.

4) Close Mail, quit Fizzilla to be sure everything was written properly (I'm not
sure if that's necessary).

5) Launch Moz, go to mail, click your Inbox.

6) Click this email.

What happens: Mozilla crashes.

At first, I thought this might be related to bug 88853, because in this build
Fizzilla crashes, but in the 0.9.3 MacOS X build Fizzilla yields the same
"Unknown 80520012" error that was listed in that bug. But then I deleted
everything related to Moz, deleted Moz 0.9.3, installed a fresh copy of 0.9.3,
and I STILL got that error message when clicking my Inbox (with no messages in
it). So, I don't know if these are related or not.

- Adam
This problem may be related to http://bugzilla.mozilla.org/show_bug.cgi?id=86775. 
Adam, would it be possible for you to get a stack trace ?
I'm willing to do anything, but I've never done that. You'd have to send me to
directions telling me exactly what I would need to do.

You can't duplicate this with the listed build?

- Adam
Oooh, learned something new today. Thanks Chris. The fact that you guys can read
this... Makes me feel like a Paclar. "Maybe he will help us with our computer
things."

;)

-----

Date/Time: 2001-08-09 19:00:26 -0700

PID:       308
Command:   Mozilla

Exception: EXC_BAD_ACCESS (0x0001)
Codes:     KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0:
 #0   0x00144694 in 0x144694 ()
 #1   0x01379cd0 in 0x1379cd0 ()
 #2   0x0012e794 in 0x12e794 ()
 #3   0x0156eff0 in 0x156eff0 ()
 #4   0x0156fd30 in 0x156fd30 ()
 #5   0x0156e2c4 in 0x156e2c4 ()
 #6   0x038e4b7c in 0x38e4b7c ()
 #7   0x038e0d64 in 0x38e0d64 ()
 #8   0x038ebe10 in 0x38ebe10 ()
 #9   0x038eba18 in 0x38eba18 ()
 #10  0x038dc7a0 in 0x38dc7a0 ()
 #11  0x038dc848 in 0x38dc848 ()
 #12  0x038eca30 in 0x38eca30 ()
 #13  0x038e99fc in 0x38e99fc ()
 #14  0x038dc7a0 in 0x38dc7a0 ()
 #15  0x038dc97c in 0x38dc97c ()
 #16  0x038eca30 in 0x38eca30 ()
 #17  0x038e536c in 0x38e536c ()
 #18  0x038f7104 in 0x38f7104 ()
 #19  0x01564168 in 0x1564168 ()
 #20  0x02285980 in 0x2285980 ()
 #21  0x02285cd0 in 0x2285cd0 ()
 #22  0x022b1b8c in 0x22b1b8c ()
 #23  0x0145a798 in 0x145a798 ()
 #24  0x014632e0 in 0x14632e0 ()
 #25  0x0017efdc in 0x17efdc ()
 #26  0x0017eec8 in 0x17eec8 ()
 #27  0x00141d84 in 0x141d84 ()
 #28  0x01582c18 in 0x1582c18 ()
 #29  0x01582aa8 in 0x1582aa8 ()
 #30  0x015a0188 in 0x15a0188 ()
 #31  0x01591770 in 0x1591770 ()
 #32  0x015911c4 in 0x15911c4 ()
 #33  0x01590cfc in 0x1590cfc ()
 #34  0x0138d14c in 0x138d14c ()
 #35  0x000919ac in 0x919ac ()
 #36  0x0009234c in 0x9234c ()

Thread 1:
 #0   0x7000424c in _syscall ()
 #1   0x706584b8 in _ProcessReadyEvent ()
 #2   0x706582b0 in _CarbonSelectThreadFunc ()
 #3   0x70014f04 in __pthread_body ()

Thread 2:
 #0   0x70059b68 in _semaphore_wait_signal_trap ()
 #1   0x70016110 in _semaphore_wait_signal ()
 #2   0x70015f78 in __pthread_cond_wait ()
 #3   0x70015d18 in _pthread_cond_wait ()
 #4   0x70653be0 in _BSD_pthread_cond_wait ()
 #5   0x70653bc0 in _CarbonConditionWait ()
 #6   0x7065557c in _CarbonOperationThreadFunc ()
 #7   0x70014f04 in __pthread_body ()

Thread 3:
 #0   0x70059b48 in _semaphore_timedwait_signal_trap ()
 #1   0x7003f7f8 in _semaphore_timedwait_signal ()
 #2   0x70015f68 in __pthread_cond_wait ()
 #3   0x7003f7c4 in _pthread_cond_timedwait_relative_np ()
 #4   0x7029b590 in _TSWaitOnConditionTimedRelative ()
 #5   0x7029cdac in _TSWaitOnSemaphoreCommon ()
 #6   0x702e5f98 in _TSWaitOnSemaphoreRelative ()
 #7   0x702e7208 in _TimerThread ()
 #8   0x70014f04 in __pthread_body ()

Thread 4:
 #0   0x70059b68 in _semaphore_wait_signal_trap ()
 #1   0x70016110 in _semaphore_wait_signal ()
 #2   0x70015f78 in __pthread_cond_wait ()
 #3   0x70015d18 in _pthread_cond_wait ()
 #4   0x7029b550 in _TSWaitOnCondition ()
 #5   0x7029cd94 in _TSWaitOnSemaphoreCommon ()
 #6   0x7029cce4 in _TSWaitOnSemaphore ()
 #7   0x7029cba8 in _AsyncFileThread ()
 #8   0x70014f04 in __pthread_body ()

Thread 5:
 #0   0x70059b68 in _semaphore_wait_signal_trap ()
 #1   0x70016110 in _semaphore_wait_signal ()
 #2   0x70015f78 in __pthread_cond_wait ()
 #3   0x70015d18 in _pthread_cond_wait ()
 #4   0x70653be0 in _BSD_pthread_cond_wait ()
 #5   0x70653bc0 in _CarbonConditionWait ()
 #6   0x70653ab4 in _CarbonInetOperThreadFunc ()
 #7   0x70014f04 in __pthread_body ()

Thread 6:
 #0   0x700007b8 in _mach_msg_overwrite_trap ()
 #1   0x700056e4 in _mach_msg_overwrite ()
 #2   0x700277b0 in _thread_suspend ()
 #3   0x70027744 in __pthread_become_available ()
 #4   0x70027468 in _pthread_exit ()
 #5   0x70014f08 in __pthread_body ()

PPC Thread State:
  srr0: 0x00144694 srr1: 0x0000f030                vrsave: 0x00000000
   xer: 0x00000018   lr: 0x0012ecdc  ctr: 0x0012ecc0   mq: 0x00000000
    r0: 0x0012e794   r1: 0xbfffe2c0   r2: 0x0025b000   r3: 0x00000000
    r4: 0xbfffe3bc   r5: 0x04092700   r6: 0x00000000   r7: 0x00000000
    r8: 0x00000000   r9: 0x00000001  r10: 0x00000001  r11: 0x6a57eae0
   r12: 0x00254118  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
   r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00269178
   r20: 0x00000000  r21: 0x00000000  r22: 0x040920a0  r23: 0x04088540
   r24: 0x038bac78  r25: 0x038ba620  r26: 0x01379cd0  r27: 0xbfffe3b4
   r28: 0x04092700  r29: 0x04092700  r30: 0x00000000  r31: 0x00000000

**********
um, well actually we can't read that stack trace but newer optimized builds 
should have macsbug symbols enabled so we can get a clue if this is in fact the 
mime bug that pchen has been working on.  Adam, can you try downloading a newer 
build and repro'ing the crash (I don't think pchen has checked in a fix yet)
Platform: PowerBook G3/300/192Mb/25Gb, MacOS X 10.0.4
Fizzilla Build: 2001082905

This appears to be fixed now. I tried clicking on the email, which properly
displayed it in my browser. I then deleted it, and Fizzilla didn't crash. So, I
think this is fixed.

- Adam
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
QA change
QA Contact: esther → stephend
This bug is gone in build 2001-08-29-05 using OS X..  I viewed it and deleted
it, without crashing.  VERIFIED FIXED.
Status: RESOLVED → VERIFIED
Attached file Test attachment
Testing problem reported in bug 93814.
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: