Closed
Bug 234404
Opened 21 years ago
Closed 17 years ago
CPU usage full on http://frog.raindrop.jp/
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: gashu, Unassigned)
References
()
Details
(Keywords: hang, Whiteboard: already fixed on trunk (both Seamonkey and Firebird))
Attachments
(1 file, 2 obsolete files)
|
346 bytes,
text/html
|
Details |
User-Agent:
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.6) Gecko/20040113
CPU usage full on http://frog.raindrop.jp/
Reproducible: Always
Steps to Reproduce:
1. Go http://frog.raindrop.jp/
2. hmm...
3. grr!!!
Actual Results:
Mozilla halts
Expected Results:
Mozilla doesn't halt
Comment 1•21 years ago
|
||
wfm FF 20040213 Win2k, CPU remains at 0%.
Not a blocker as per http://bugzilla.mozilla.org/bug_status.html#severity
Severity: blocker → critical
Keywords: hang
Comment 2•21 years ago
|
||
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7a) Gecko/20040214
http://frog.raindrop.jp/styles-site.css validates,
http://frog.raindrop.jp/index.rdf validates.
WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206
Firefox/0.8
Comment 4•21 years ago
|
||
WFM
Comment 5•21 years ago
|
||
Sorry, I thought User Agent string would be attached. I haven't found any
significant CPU usage at the site. Mozilla 1.6 under Windows XP Professional.
Comment 6•21 years ago
|
||
WFM: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040214
Firebird/0.8.0+
I'm going to resolve this bug as WORKSFORME since I also see this bug and there
are already 4 other people that also dont see this.
Reporter: you can try to use a newer nightly build of Mozilla from
ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/ A new
profile may also fix your problem.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Sorry, I should have make it sure using latest-trunk.
I can NOT reproduce this using
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040215
I can reproduce using Moz1.6Fin/MozFx 0.8 under WinXP though.
Comment 8•21 years ago
|
||
Okay, I was able to reproduce this using Firefox 0.8 (which has a build ID of
20040210). Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a)
Gecko/20040214 Firebird/0.8.0+ does not cause this problem. It seems that
something was changed within the last few days that fixed this problem (Or it
was a problem that has since been fixed on the trunk).
Either way, the new builds do now have this problem.
| Reporter | ||
Comment 10•21 years ago
|
||
This problem is reproducible using Mozilla 1.4.1.
Reopening and changing version to 1.4 branch.
NOTE: Please try testcase with small browser window.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Version: Trunk → 1.4 Branch
| Reporter | ||
Comment 11•21 years ago
|
||
reduced HTML code of refered URL.
Sorry for my mistake..
Attachment #141593 -
Attachment is obsolete: true
Comment 12•21 years ago
|
||
Confirmed:
Reproducable on Firefox 0.8 release under Win2k. Also upon starting task manager
I see the Firefox memory usage is constantly increasing. The system is almost stale
Comment 13•21 years ago
|
||
Artem: please see comment 8. Firefox 0.8 release has this problem but the
lastest versions build off the trunk do not experience this.
Whiteboard: already fixed on trunk (both Seamonkey and Firebird)
| Reporter | ||
Comment 14•21 years ago
|
||
reduced/modified HTML code of refered URL.
After the conversation with the author of the website
<http://frog.raindrop.jp>, he/she is considering revising the page that this
problem occured. In addition, he/she presented better test case. And if <pre>
is <pre style="width: 300px"> , this problem is not occured.
# see comment 8 first. This problem is already fixed on trunk.
Attachment #141595 -
Attachment is obsolete: true
Comment 15•21 years ago
|
||
ok, not blocking 1.7a which is coming from the trunk.
Flags: blocking1.7a? → blocking1.7a-
Comment 16•21 years ago
|
||
anyone know what fixed it?
Comment 17•21 years ago
|
||
Without a patch, blocking 1.4.2 is useless.
If someone can tell me what fixed it...
Flags: blocking1.4.2? → blocking1.4.2-
| Reporter | ||
Comment 18•21 years ago
|
||
Micheal, When is 1.4.2 release date planed? It is not yet clearly announced in
Mozilla.org's roadmap. If it is so soon, I will ask people to find out what
fixed this, to people in MozillaZine or people in MozillaGumi, JA community site
which this bug was originally reported.
IMO, this bug should be fixed for Mozilla's reliability. Maybe especially for
some corp providing 1.4.x based Linux desktop environment. This means competitor
or anti-Mozilla people can easily point its weakness using attachement 141611.
# So I will turn blocking flag back to "?", If the target date is soon, or it is
not realistic, you can turn it to "-" again.
Comment 19•21 years ago
|
||
The target date is ASAP.
Please investigate this quickly. If you have something by tomorrow, I'll
consider it.
| Reporter | ||
Comment 20•21 years ago
|
||
I see. I'll do my best.
If any constractive response is unavailable by 2004-02-26 12:00 PST,
Please return the flag back to "-".
Comment 21•21 years ago
|
||
WFM: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6)
Gecko/20040206 Firefox/0.8 under MacOSX10.2.8
Comment 22•21 years ago
|
||
I tested it on trunk/nightly build.
1/9 reproduced. 1/10 not reproduced. both firebird and seamonkey.
Comment 23•21 years ago
|
||
I tested the build. 2004-1-9 9:00 reproduced 2004-1-9 12:00 not reproduced.
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=MozillaTinderboxAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=01%2F09%2F2004+09%3A00%3A00&maxdate=01%2F09%2F2004+12%3A00%3A00&cvsroot=%2Fcvsroot
Path of bug 210269 seems to resolve this bug.
Comment 24•21 years ago
|
||
noririty and I tested.
before bug 210269. reproduced.
after bug 210269. not reproduced.
patch of bug 210269 resolved it.
Comment 25•21 years ago
|
||
*** This bug has been marked as a duplicate of 210269 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 21 years ago
Resolution: --- → DUPLICATE
Comment 26•21 years ago
|
||
210269 is not the source of this problem. This problem is fixed on the trunk so
I am going to mark it fixed.
I'm sorry, this isn't going into 1.4.
Status: RESOLVED → UNCONFIRMED
Flags: blocking1.4.2? → blocking1.4.2-
Resolution: DUPLICATE → ---
Comment 27•21 years ago
|
||
incidentally I don't see the problem on the current 1.4 branch build, so maybe
this is OK anyway.
WORKSFORME is the appropriate close code since there is no fix in this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 21 years ago
Resolution: --- → WORKSFORME
Comment 28•21 years ago
|
||
Reopening because Wrong Resolution.
I can still see this on:
Mozilla 1.4.2
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4.2) Gecko/20040227
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 29•21 years ago
|
||
This bug occured by infinity reflow loop caused by scroll bar.
Make dependency to bug 210269.
and mark as NEW
Status: UNCONFIRMED → NEW
Component: Browser-General → Layout: Misc Code
Depends on: 210269
Ever confirmed: true
Assignee: general → nobody
QA Contact: general → core.layout.misc-code
Comment 30•20 years ago
|
||
If I load attachment 141611 [details] in a small window and then scroll left and rigth, I
do not notice any significant cpu usage or any significant cpu modification
while using Mozilla 1.8b2 build 2005061105 under XP Pro.
Is this bug specific to the 1.4 Branch?
Comment 31•17 years ago
|
||
=> INVALID attachment 141611 [details] testcase no longer scrolls
and bug 210269?
Status: NEW → RESOLVED
Closed: 21 years ago → 17 years ago
Resolution: --- → INVALID
Updated•7 years ago
|
Product: Core → Core Graveyard
| Assignee | ||
Updated•7 years ago
|
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•