Closed
Bug 622634
Opened 14 years ago
Closed 13 years ago
[OGL] Occasional corruption on Nexus One with accelerated layers
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 621745
Tracking | Status | |
---|---|---|
fennec | + | --- |
People
(Reporter: jrmuizel, Assigned: BenWa)
References
Details
Sometimes I get greenish garbage on the screen.
Reporter | ||
Updated•14 years ago
|
Blocks: opengl-mobile
Reporter | ||
Comment 1•14 years ago
|
||
Sometimes I also content duplicated.
Updated•14 years ago
|
tracking-fennec: --- → ?
OS: Mac OS X → Android
Hardware: x86 → ARM
Updated•13 years ago
|
Summary: Occasional corruption on Nexus One with accelerated layers → [OGL] Occasional corruption on Nexus One with accelerated layers
Updated•13 years ago
|
tracking-fennec: ? → 2.0b4+
Updated•13 years ago
|
tracking-fennec: 2.0b4+ → 2.0next+
Updated•13 years ago
|
tracking-fennec: 2.0next+ → 7+
Reporter | ||
Comment 2•13 years ago
|
||
Does this still happen?
Comment 4•13 years ago
|
||
This happens because we're drawing textures at the wrong location. The Android window is resized when the keyboard opens or closes, and it seems that we're double-correcting for that resizing on the first draw after the resize.
Updated•13 years ago
|
tracking-fennec: 7+ → +
Assignee | ||
Comment 5•13 years ago
|
||
Can't reproduce this with m-c. It could be particular to patches that haven't landed such as heeen's queue.
Assignee | ||
Comment 6•13 years ago
|
||
(In reply to comment #5) > Can't reproduce this with m-c. It could be particular to patches that > haven't landed such as heeen's queue. Nevermind, I can reproduce this on m-c without patches applied.
Assignee | ||
Updated•13 years ago
|
Assignee: joe → bgirard
Assignee | ||
Comment 7•13 years ago
|
||
(In reply to comment #4) > This happens because we're drawing textures at the wrong location. The > Android window is resized when the keyboard opens or closes, and it seems > that we're double-correcting for that resizing on the first draw after the > resize. What you describe is exactly bug 621745. Are there any different corruptions occurring for this bug or should we resolve as duplicate?
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•