Clean backport to jfx21u. This backport was already requested and approved in
JBS.
-
Commit messages:
- Backport b80ec391cbba72d84b4b862b3f1b8db2ff8eb6e2
Changes: https://git.openjdk.org/jfx21u/pull/37/files
Webrev: https://webrevs.openjdk.org/?repo=jfx21u=37=00
Issue:
On Mon, 27 Nov 2023 20:22:40 GMT, Thorsten Fischer wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
On Mon, 27 Nov 2023 20:22:40 GMT, Thorsten Fischer wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
On Mon, 27 Nov 2023 20:22:40 GMT, Thorsten Fischer wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
On Mon, 27 Nov 2023 20:22:40 GMT, Thorsten Fischer wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
On Mon, 27 Nov 2023 20:22:40 GMT, Thorsten Fischer wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
On Mon, 27 Nov 2023 19:57:30 GMT, Thorsten Fischer wrote:
>> I have put this in D3DContext.java (as per customer suggestion). Just
>> wondering if I should just reinitialize directly and not wait loop: in
>> testLostStateAndReset in D3DContext.java (D3DERR_DEVICEREMOVED is handled
>> further
On Mon, 27 Nov 2023 20:22:40 GMT, Thorsten Fischer wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
On Mon, 27 Nov 2023 20:22:40 GMT, Thorsten Fischer wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
On Mon, 27 Nov 2023 20:22:40 GMT, Thorsten Fischer wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
On Mon, 27 Nov 2023 20:22:40 GMT, Thorsten Fischer wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
On Mon, 27 Nov 2023 20:22:40 GMT, Thorsten Fischer wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
> Hi,
>
> I did open the bug report. Some notes to this PR:
>
> My colleagues and I are able to reproduce this bug regularly, even though it
> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
> up. We are currently evaluating two versions of fixes, but until now we do
On Mon, 27 Nov 2023 15:00:30 GMT, mintykat wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We are
On Wed, 22 Nov 2023 20:44:58 GMT, Marius Hanl wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We are
On Sat, 5 Aug 2023 12:28:16 GMT, Thorsten Fischer wrote:
> Hi,
>
> I did open the bug report. Some notes to this PR:
>
> My colleagues and I are able to reproduce this bug regularly, even though it
> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
> up. We are
On Sat, 5 Aug 2023 12:28:16 GMT, Thorsten Fischer wrote:
> Hi,
>
> I did open the bug report. Some notes to this PR:
>
> My colleagues and I are able to reproduce this bug regularly, even though it
> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
> up. We are
On Sat, 5 Aug 2023 12:28:16 GMT, Thorsten Fischer wrote:
> Hi,
>
> I did open the bug report. Some notes to this PR:
>
> My colleagues and I are able to reproduce this bug regularly, even though it
> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
> up. We are
On Sat, 5 Aug 2023 12:28:16 GMT, Thorsten Fischer wrote:
> Hi,
>
> I did open the bug report. Some notes to this PR:
>
> My colleagues and I are able to reproduce this bug regularly, even though it
> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
> up. We are
On Tue, 7 Nov 2023 07:26:31 GMT, Michael Strauß wrote:
> On a side note, I think we should remove the non-9Ex code paths from the D3D
> pipeline. We're not supporting Windows XP, are we?
This might be a good follow-up issue to file. We no longer support nor run on
Windows XP (or Windows
On Sat, 5 Aug 2023 12:28:16 GMT, Thorsten Fischer wrote:
> Hi,
>
> I did open the bug report. Some notes to this PR:
>
> My colleagues and I are able to reproduce this bug regularly, even though it
> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
> up. We are
On Sat, 5 Aug 2023 12:28:16 GMT, Thorsten Fischer wrote:
> Hi,
>
> I did open the bug report. Some notes to this PR:
>
> My colleagues and I are able to reproduce this bug regularly, even though it
> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
> up. We are
On Sat, 5 Aug 2023 13:36:23 GMT, Kevin Rushforth wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We
On Sat, 5 Aug 2023 12:28:16 GMT, Thorsten Fischer wrote:
> Hi,
>
> I did open the bug report. Some notes to this PR:
>
> My colleagues and I are able to reproduce this bug regularly, even though it
> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
> up. We are
On Sun, 3 Sep 2023 12:46:00 GMT, Thorsten Fischer wrote:
> Our observations with current proposal ("Version 1"): When the error
> occurred, the state did not go into D3D_OK again, but it stayed at
> D3DERR_DEVICEHUNG. The D3DERR_DEVICEHUNG error message was printed over and
> over (for > 1
On Sat, 5 Aug 2023 12:28:16 GMT, Thorsten Fischer wrote:
> Hi,
>
> I did open the bug report. Some notes to this PR:
>
> My colleagues and I are able to reproduce this bug regularly, even though it
> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
> up. We are
On Sat, 5 Aug 2023 12:28:16 GMT, Thorsten Fischer wrote:
> Hi,
>
> I did open the bug report. Some notes to this PR:
>
> My colleagues and I are able to reproduce this bug regularly, even though it
> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
> up. We are
On Tue, 8 Aug 2023 17:54:03 GMT, Marius Hanl wrote:
>> Hi,
>>
>> I did open the bug report. Some notes to this PR:
>>
>> My colleagues and I are able to reproduce this bug regularly, even though it
>> takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows
>> up. We are
Hi,
I did open the bug report. Some notes to this PR:
My colleagues and I are able to reproduce this bug regularly, even though it
takes sometimes up to 3 or 4 weeks until the D3DERR_DEVICEHUNG error shows up.
We are currently evaluating two versions of fixes, but until now we do not have
any
29 matches
Mail list logo
