none
What is the meaning of this output: 'Element not found'? RRS feed

  • Question

  • What does this mean ..

    onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!00007FFC79C804B0: (caller: 00007FFC79C801F5) ReturnHr(1) tid(2318) 80070490 Element not found.

    The app at this stage is a simple UWP/Xaml/SharpDX app that does some raytracing.

    Here's output showing it trigger on window resizing ..

    T: 3 | CoreRenderer.Ctor
    T: 3 | MainPage.Loaded: 1254,888
    T: 3 | RasterizerStatePrefabs.BuildSolid
    T: 3 | Texture.Ctor [TextureRectRenderer.debugTexture]
    onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!00007FFC79C804B0: (caller: 00007FFC79C801F5) ReturnHr(1) tid(5f38) 80070490 Element not found.
    onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!00007FFC79C804B0: (caller: 00007FFC79C801F5) ReturnHr(2) tid(5f38) 80070490 Element not found.
    T: 3 | MainPage.SizeChanged: 1197,774
    T: 3 | Texture.Ctor [TestRenderer.Texture]
    onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!00007FFC79C804B0: (caller: 00007FFC79C801F5) ReturnHr(3) tid(5f38) 80070490 Element not found.
    onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!00007FFC79C804B0: (caller: 00007FFC79C801F5) ReturnHr(4) tid(5f38) 80070490 Element not found.
    T: 3 | MainPage.SizeChanged: 2028,1348
    T: 3 | Texture.Ctor [TestRenderer.Texture]
    onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!00007FFC79C804B0: (caller: 00007FFC79C801F5) ReturnHr(5) tid(5f38) 80070490 Element not found.
    onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!00007FFC79C804B0: (caller: 00007FFC79C801F5) ReturnHr(6) tid(5f38) 80070490 Element not found.
    T: 3 | MainPage.SizeChanged: 1197,774
    T: 3 | Texture.Ctor [TestRenderer.Texture]

    Sunday, November 3, 2019 5:16 AM

All replies

  • Hi,

    I can reproduce this issue in vs2019 in version 1903, what's about your system version and project version? In addition, I researched about it but did not find something useful. I'm not sure what caused this behavior. I'll need to ask other engineers about this issue. There might be some time delay.

    Best Regards,

    Fay


    "Developing Universal Windows apps" forum will be migrating to a new home on Microsoft Q&A (Preview)!
    We invite you to post new questions in the "Developing Universal Windows apps" forum’s new home on Microsoft Q&A (Preview)!
    For more information, please refer to the sticky post.


    Monday, November 4, 2019 8:45 AM
  • Hi,

    >>What does this mean of 'Element not found'

    The error "Element not found" especially occurs when window's size changes, it feels that it is caused by the grid is not fully loaded when the size changes.

    About this exception, Windows use exceptions and catch them at different level. For your end user, they should not see this exception and app should not crash. So it may be a first chance exception and handle by the system already. You can continue to do the programming and don't worry about it.

    Best Regards,

    Fay


    "Developing Universal Windows apps" forum will be migrating to a new home on Microsoft Q&A (Preview)!
    We invite you to post new questions in the "Developing Universal Windows apps" forum’s new home on Microsoft Q&A (Preview)!
    For more information, please refer to the sticky post.

    Wednesday, November 6, 2019 8:19 AM
  • OK. It seems like there's something wrong then, because the grid is loaded. These are resizing events after the window is built and when I'm already rendering.
    Thursday, November 14, 2019 2:56 PM