Extremely slow scrolling using scroll bar on right side of browser. Also, when I went to report this bug earlier, Mozilla browser crashed (for the umpteenth time today).
Please ALWAYS include your Mozilla build ID with the bug report. Thank you.
Build ID 2002071508
Summary: Extremely Slow Scrolling & Multiple Browser Crashes → Extremely Slow Scrolling & Multiple Browser - Crashes Build ID 2002071508
I've experienced no problems with that build
WorksForMe using FizzillaCFM/2002071508. Mac Sew, please report the crasher as a separate bug using the Bugzilla Helper at [http://www.mozilla.org/quality/help/bug-form.html], and attach a crash report. Since Mac OS X builds don't include TalkBack, always try to file a bug whenever it crashes. About this bug: can you reproduce this problem using a new Mozilla user profile? (Sending to XP Toolkit/Widgets.)
Assignee: Matti → jaggernaut
Severity: major → normal
Component: Browser-General → XP Toolkit/Widgets
QA Contact: asa → jrgm
Summary: Extremely Slow Scrolling & Multiple Browser - Crashes Build ID 2002071508 → Extremely slow scrolling using scroll bar on right side of browser
This bug report does not have sufficient steps to reproduce to be valid.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
It is not my intention, or anyone else's, to discourage people from finding and reporting bugs. But it is also not my intention to waste engineer's time dealing with incomplete and undefined bug reports. Please read: http://www.mozilla.org/quality/bug-writing-guidelines.html http://www.mozilla.org/quality/browser/prescreening.html particularly with respect to 'reproducible' and 'specific'. If you have additional details that would allow an engineer to address your problem in an effective way, then reopen this bug. > 2) I don't see the connection to XP? This is not on the Windows XP OS; > it's on Mac OS X. If you read the definitions of the "XP..." components (click on 'Component' link in this bug report) you will see that XP is shorthand for "cross platform" and has nothing specifically to do with Windows XP. In practice, XP Toolkit is the home of bugs relating to bugs in the core functionality of the UI, such as a scrollbar problem. [Of course, 'Browser General' is a suitable rest home for unspecific bug reports, but I digress].
Responding to points in an e-mail that "Mac Sew" sent jaggernaut: 1) The bug was marked invalid as it does not provide enough detail to do any troubleshooting. Details such as exactly what kind of Mac (slow is a very relative term) and what site(s) exhibit the slowness. As for crashes, internally we find Mozilla very stable on Mac OS X. Not to say there aren't some sites that might not cause it to crash but without knowing what site and how to reproduce it we can't really find and fix the problem. If Mozilla is repeatedly crashing for you please log a bug with these details and then attach a Mozilla crash log to the bug. Crash logging is enabled in the preferences panel of the Console application (in /Applications/Utilities). Turn on the "Log crash information..." and "Automatically display..." prefs and any time an OS X app crashes the console app will display data that will hopefully be useful in determining why the crash occured. 3) Regarding the stability of the build, these days it's generally quite high and a couple of other people noted in the bug that they saw no problems with the 2002071508 build. If you are using a nightly build consider it a thrill seekers/bleeding edge build and not a 'release' build. A nightly build doesn't get QA verification before being posted (it's posted _for_ QA review). And keep in mind that, like most people, QA engineers don't work on the weekends. 4) External bug reports are very useful but _only_ if they contain specific, and preferably reproducable, information on the problem that is being observed. If you'd like to add the information described we can certainly re-open the bug (that's why the option is there :-)
I wonder if this is related to bug 157837 ?
vrfy invalid yes it's quite possible it was that bug. reporter: the bug referenced was fixed 8/1.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.