Closed
Bug 681791
Opened 14 years ago
Closed 14 years ago
When trying to create a too large canvas, don't throw, instead just use a smaller drawing buffer
Categories
(Core :: Graphics: CanvasWebGL, defect)
Core
Graphics: CanvasWebGL
Tracking
()
RESOLVED
FIXED
mozilla10
People
(Reporter: bjacob, Assigned: jgilbert)
References
()
Details
Attachments
(1 file, 5 obsolete files)
|
19.35 KB,
patch
|
jgilbert
:
review+
|
Details | Diff | Splinter Review |
We currently file a few WebGL conformance tests, like
https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/sdk/tests/conformance/canvas/drawingbuffer-static-canvas-test.html
Because we throw on canvas.width = something_huge when SetDimensions fails.
Chrome doesn't throw there.
Chrome also won't use a drawingbuffer larger than the max texture size or 4k, whichever is smaller.
We need to fail less on resizing-canvases-to-large-sizes by using a smaller drawingbuffer if needed.
| Assignee | ||
Updated•14 years ago
|
| Assignee | ||
Updated•14 years ago
|
Blocks: webgl-conformance
| Assignee | ||
Updated•14 years ago
|
Assignee: nobody → jgilbert
| Assignee | ||
Updated•14 years ago
|
| Assignee | ||
Comment 1•14 years ago
|
||
This change basically guarantees that GLContext will not be changed if a resize attempt fails.
| Assignee | ||
Comment 2•14 years ago
|
||
It didn't occur to me before that the arguably time-saving initialize once approach was incompatible with soft-failing resizing.
Updated try: https://tbpl.mozilla.org/?tree=Try&usebuildbot=1&rev=322fe6cae175
| Assignee | ||
Comment 3•14 years ago
|
||
Yeah, that didn't work so well.
Updated:
https://tbpl.mozilla.org/?tree=Try&usebuildbot=1&rev=089d1b13072f
| Assignee | ||
Updated•14 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 4•14 years ago
|
||
Current patch file.
Attachment #564827 -
Attachment is obsolete: true
Attachment #566099 -
Flags: review?(bjacob)
| Assignee | ||
Updated•14 years ago
|
Attachment #566099 -
Flags: review?(bjacob) → feedback?(bjacob)
| Assignee | ||
Comment 5•14 years ago
|
||
Ran into a problem on OS X.
| Assignee | ||
Comment 6•14 years ago
|
||
Fixed CGL impl.
Attachment #566099 -
Attachment is obsolete: true
Attachment #566099 -
Flags: feedback?(bjacob)
Attachment #566404 -
Flags: review?(bjacob)
| Assignee | ||
Comment 7•14 years ago
|
||
New try run:
https://tbpl.mozilla.org/?tree=Try&rev=5a9f76410202
| Assignee | ||
Comment 8•14 years ago
|
||
For some reason my last changes reset. Maybe I reset my patch file somehow.
Updated try with CGL fix:
https://tbpl.mozilla.org/?tree=Try&rev=ff8c9387530d
| Assignee | ||
Comment 9•14 years ago
|
||
Fixed errant tab issues and added further commenting.
Attachment #566404 -
Attachment is obsolete: true
Attachment #566404 -
Flags: review?(bjacob)
Attachment #567141 -
Flags: review?(bjacob)
| Assignee | ||
Comment 10•14 years ago
|
||
Predicates too-verbose debug printf on mDebugMode.
Attachment #567141 -
Attachment is obsolete: true
Attachment #567141 -
Flags: review?(bjacob)
Attachment #567147 -
Flags: review?(bjacob)
| Reporter | ||
Comment 11•14 years ago
|
||
Comment on attachment 567147 [details] [diff] [review]
Guarantees that GLContext::ResizeOffscreen is harmless if it fails
Review of attachment 567147 [details] [diff] [review]:
-----------------------------------------------------------------
This looks all good!
Just one remark about something to keep in mind. The ClearSafely() call is mega-super-important for security: we must prevent WebGL scripts from reading back uninitialized video memory from a newly resized canvas. In your AA patches, the FBO becomes two separate FBOs, right. So will we need two ClearSafely() calls there?
Attachment #567147 -
Flags: review?(bjacob) → review+
| Assignee | ||
Comment 12•14 years ago
|
||
> Just one remark about something to keep in mind. The ClearSafely() call is
> mega-super-important for security: we must prevent WebGL scripts from
> reading back uninitialized video memory from a newly resized canvas. In your
> AA patches, the FBO becomes two separate FBOs, right. So will we need two
> ClearSafely() calls there?
I will triple-check, but we shouldn't need to. After clearing the draw buffer, the read buffer /may/ be uninitialized, but before any read call is possible, we blit over the cleared draw buffer, clearing the read buffer. Basically, it's only possible to access if you can read it without using GL commands to do so. We could just deliberately blit over the cleared draw buffer, as that should be minimal cost compared to assembling a resized buffer, but it should not be necessary. If it were necessary, there would be other problems with our WebGL restrictions anyways.
| Assignee | ||
Comment 13•14 years ago
|
||
Carrying forward r+ from bjacob after PR_TRUE/FALSE conversion.
Attachment #567147 -
Attachment is obsolete: true
Attachment #567820 -
Flags: review+
| Reporter | ||
Comment 14•14 years ago
|
||
| Reporter | ||
Comment 15•14 years ago
|
||
Re-landed with proper commit message (sorry, should have checked that)
http://hg.mozilla.org/integration/mozilla-inbound/rev/716915ed489c
Comment 16•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla10
You need to log in
before you can comment on or make changes to this bug.
Description
•