locked
Access violation exception after tap on GridView's item

    Question

  • My application crashes when I tap on item in GridView which can be manipulated. The exception is Access violation. I created a simple application which raises this exception and documented it on Microsoft Connect. I'm able to reproduce it on device with ARM processor only.

    This looks like a similar bug found 2 years ago. However there is not any manipulation in progress during tap event.

    Is it a known issue? I'm looking for a workaround (or what I made wrong).



    • Edited by Václav Dajbych Tuesday, January 06, 2015 9:37 AM more accurate expression
    Monday, January 05, 2015 10:30 AM

Answers

  • Hello there,

    I have investigated into the problem you are experiencing and this issue has turned out to be a bug in the XAML Input manager framework. Unfortunately there is no good fix or workaround to this problem on Windows/ Phone 8.1.

    We are definitely tracking this issue for Windows 10, but until that happens, you are probably better off without using the ManipulationMode if you don't really require it.

    Thanks,

    Prashant


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Tuesday, January 13, 2015 2:10 AM
    Moderator

All replies

  • Thanks for reporting the issue. I will take a look into this and get back to you...

    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Tuesday, January 06, 2015 1:02 AM
    Moderator
  • Hello...Just wanted to let you know that I am still investigating into this...With the simple app I can see that the app crashes only when the ManipulationMode of the User control is set. If the ManipulationMode parameter is removed, then the app does not crash.

    Are you experiencing this crash only on the Phone or does it crash even on Windows?


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Saturday, January 10, 2015 1:08 AM
    Moderator
  • Hello there,

    I have investigated into the problem you are experiencing and this issue has turned out to be a bug in the XAML Input manager framework. Unfortunately there is no good fix or workaround to this problem on Windows/ Phone 8.1.

    We are definitely tracking this issue for Windows 10, but until that happens, you are probably better off without using the ManipulationMode if you don't really require it.

    Thanks,

    Prashant


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Tuesday, January 13, 2015 2:10 AM
    Moderator
  • I assumed this is a bug, therefore I created a reproducible case. Thank you for investigation. I'm looking forward to Windows 10.
    Tuesday, January 13, 2015 8:36 AM