RFR: 8185862: AWT Assertion Failure in ::GetDIBits(hBMDC, hBM, 0, 1, 0, gpBitmapInfo, 0) 'awt_Win32GraphicsDevice.cpp', at line 185
Matthias Baesken
mbaesken at openjdk.org
Mon Jan 29 14:49:47 UTC 2024
- Previous message (by thread): RFR: 8185862: AWT Assertion Failure in ::GetDIBits(hBMDC, hBM, 0, 1, 0, gpBitmapInfo, 0) 'awt_Win32GraphicsDevice.cpp', at line 185
- Next message (by thread): RFR: 8185862: AWT Assertion Failure in ::GetDIBits(hBMDC, hBM, 0, 1, 0, gpBitmapInfo, 0) 'awt_Win32GraphicsDevice.cpp', at line 185
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Mon, 29 Jan 2024 14:24:43 GMT, Christoph Langer <clanger at openjdk.org> wrote:
>However, it seems to be some kind of a pseudo device where you can not get a DC via CreateDC. This behavior/monitor type
> doesn't seem to be well documented, though.
This was my observation too, but is it always the case ? Unfortunately I couldn't find some documentation on this.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/17614#issuecomment-1914843748
- Previous message (by thread): RFR: 8185862: AWT Assertion Failure in ::GetDIBits(hBMDC, hBM, 0, 1, 0, gpBitmapInfo, 0) 'awt_Win32GraphicsDevice.cpp', at line 185
- Next message (by thread): RFR: 8185862: AWT Assertion Failure in ::GetDIBits(hBMDC, hBM, 0, 1, 0, gpBitmapInfo, 0) 'awt_Win32GraphicsDevice.cpp', at line 185
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the client-libs-dev
mailing list