Closed Bug 242297 Opened 20 years ago Closed 20 years ago

Quicktime 6.5.1 and Mozilla 1.7rc1 Very buggy and unstable. [js_Mark] [nsFrame::IsVisibleForPainting]

Categories

(Core Graveyard :: Plug-ins, defect)

PowerPC
macOS
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: pbergsagel, Assigned: peterlubczynski-bugs)

Details

Attachments

(4 files)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040218 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040218 I installed the latest Quicktime security update from version 6.5 to 6.5.1 . Mozilla became unstable after this update. It would either quit unexpectedly or cause a kernel panic. Mozilla's instability became worse afer I played an mpg4 using the quicktime plugin (not the external app [could not test using the external app]). I downgraded to 1.7b from April 11 with little improvment. When I downgraded to Mozilla 1.7a from Feb 21 Mozilla's stability returned and the newly upgraded Quicktime plugin worked with Mozilla. Reproducible: Always Steps to Reproduce: 1.Play a quicktime file using the Quicktime plugin 6.5.1 using Mozilla 1.7rc1. 2.Mozilla will either crash as it plays the quicktime file or create an instability within Mozilla so it will crash with in 1-10 minutes after the quicktime file was played. 3. Sometimes while I am reading text on a web page the "spinning beach ball" will appear within a few seconds Mozilla quits. Actual Results: Before upgrading to Quiktime 6.5.1 I was using Moz 1.7b from April 11 and it was stable. I had little issues with stability. After up grading to Quicktime 6.5.1 from 6.5 stability became a major issue with Mozilla. I repaired the hard drive permissions and rebound the prebindings. I upgraded to Moz 1.7brc1 and Moz was still unstable and would crash when/after using the quicktime 6.5.1 plugin. Finally I downgraded to Mozilla 1.7b (Feb 21). Finally using version 1.7a Mozilla was stable and plays the Quictime 6.5.1 content using the plug perfectly. I have not had a crash in over 2 hours now. I used the same user profile and did not create a new one. Expected Results: Mozilla should not have become unstable or crashed with version 1.7rc1. I have come to the conclusion that there is some incompatility between Mozilla (1.7b (only tested Feb 21) and 1.7b rc1). I beleive that this instability began after I upgraded to Quicktime 6.5.1 and before I played a Quicktime file, though I am not sure.
Attached file First crash log
This crash log has sections which are both similar and different from the next crash log.
Attached file second crash log
Any chance of crash logs as plaintext?
Attachment #147471 - Attachment mime type: application/octet-stream → text/plain
Attachment #147472 - Attachment mime type: application/octet-stream → text/plain
Summary: Quicktime 6.5.1 and Mozilla 1.7rc1 Very buggy and unstable. → Quicktime 6.5.1 and Mozilla 1.7rc1 Very buggy and unstable. [js_Mark] [nsFrame::IsVisibleForPainting]
I believe I have resolved this issue. I will reopen this bug again if the bug reappears. I resolved this bug by running the freeware utility program Onyx (a very good utility all OS X users should download). I ran Onyx and opened the Automate tab. I checked these options: -execute all maintainace scripts -delete internet caches and history -delete user caches files -delete system cache files -delete -archive logs -crash reporter -recent servers -core.xxx files I shut down the computer (waited one minute) and restarted. All was fine with Mozilla and Quicktime. No more unepected quits. Quicktime files play smoothly. All is as it should be. :) My conclusion is that MacOS X requires more maintenace than pre-OS X operating systems. If this maintenace is neglected over time, the Operating System can begin acting strangely. I you use OS X run a maintenace utility such as Onyx at least once a month or suffer from an OS which may begin acting up. I am closing this bug as WORKSFORME since this is very likely not a Mozilla bug but rather an issue oresulting from my lack of OS X maintenace.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: