RFR: 8352209: NPE com.sun.prism.d3d.D3DTextureData.getContext [v3]

[Lukasz Kostyra]

On Mon, 3 Nov 2025 13:35:26 GMT, Alessadro Parisi <duke at openjdk.org> wrote:

> I read that it’s possible to control the amount of VRAM through the prism.maxvram system property. What happens if I set a value much larger than the available VRAM? Does it automatically fall back to system RAM on both iGPUs and dGPUs?

In most cases this is in hands of the runtime and the driver. In D3D and ES2 during allocation we provide those with a hint on how the memory is used and the runtime/driver determine the best spot for it. When VRAM runs out most drivers will delegate such allocation to system RAM making it slower to access (especially on dGPUs; iGPUs often share RAM memory with the system already) but keeping the application alive.

Modern APIs are more explicit about this - both Vulkan and D3D12 need you to specify (at least to some degree) which memory type you want your newly allocated region to exist in - but this is not the problem in case of JavaFX (yet =) ).

-------------

PR Comment: https://git.openjdk.org/jfx/pull/1951#issuecomment-3484142333