On Tue, 20 Oct 2026 18:26:30 GMT, Andy Goryachev <[email protected]> wrote:
>> This is a pre-existing limitation also for Canvas under the SW pipeline >> (where it fails just as silently). I think this is better addressed >> separately as a solution may be involved. > > I recall `Canvas` failing with smaller dimensions due to failed allocation, > but I don't have the record. Even more, the `Canvas` is intended to be > displayed on screen, so we don't expect it to be too large, right? > > With the DC API, we might actually expect users creating giant contexts. > Should we explicitly mention the size limit in the constructor? Canvas indeed also has problems when you exceed the texture size of the GPU, so you can't make a 100k x 1 Canvas. The problem there is that it isn't as easily solved with tiling as drawing operations that cross textures are hard to get right. Images have no such problems as the operations always happen on a single chunk of memory, and tiling only happens afterwards. As for a size limit, I suppose we can mention it as a known limitation, but it is one that can be removed with more work (unlike a tiled Canvas, which is a much harder problem), so it shouldn't be part of the specification. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/1969#discussion_r4331517953
