locked
Bug report: Windows 8 runtime crashes on startup

    Question

  • In a Javascript-based app, when accessing

        Windows.Globalization.ApplicationLanguages.languages

    immediately on startup, the app crashes with the following stacktrace

        ntdll.dll!RtlpCaptureContext()
        ntdll.dll!RtlpWalkFrameChain()
        ntdll.dll!RtlWalkFrameChain()
        ntdll.dll!RtlCaptureStackBackTrace()
        ntdll.dll!RtlpLogHeapFailure()
        ntdll.dll!RtlFreeHeap()
        msvcrt.dll!free()
        BCP47Langs.dll!Windows::Internal::CLanguage::`vector deleting destructor'()
        fffffffffffffffe()
        0000003d39c8fa08()
        0000003d39c8fa08()
        MrmCoreR.dll!Microsoft::Resources::UserLanguageProfileQVProvider::GetQualifierValue(struct Microsoft::Resources::Atom,class Microsoft::Resources::IProviderDataSources const *,class Microsoft::Resources::IDefStatus *,class Microsoft::Resources::IStringResult *)
         MrmCoreR.dll!Windows::ApplicationModel::Resources::Core::LanguageChangeNotifiyThreadProc(void *)
         kernel32.dll!BaseThreadInitThunk()
         ntdll.dll!RtlUserThreadStart()

    Thursday, August 15, 2013 4:21 PM

Answers

All replies

  • Please post a simple repro and steps to create the issue.

    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Thursday, August 15, 2013 6:43 PM
    Moderator
  • I would if I could. Just putting this single line of code into a new project doesn't produce the error but it disappears when removing the line or putting a timeout promise around it. A few times I could even reproduce it in the debugger, stepping into it.

    But part of the problem is that the access violation doesn't occur every time, as it seems to be some kind of race condition.

    Also, lately I find it has been occurring more regularly, especially when starting the app in Release mode. Unfortunately in this special case I need to check the available languages immediately when loading the app in order to load a 3rd-party library using the correct language, so a timeout-Promise isn't an option here.

    You can see from the short stacktrace that our application code isn't involved at any point: it's a brand new thread started by the runtime to notify listeners about a language change. Maybe a missing critical section or who knows what - all I know that it crashes when accessing the `languages` property.

    Friday, August 16, 2013 11:46 AM
  • OK, thanks for reporting it.  Without some sort of repro however there is nothing I can do with the report unfortunately.

    Jeff Sanders (MSFT)

    @jsandersrocks - Windows Store Developer Solutions @WSDevSol
    Getting Started With Windows Azure Mobile Services development? Click here
    Getting Started With Windows Phone or Store app development? Click here
    My Team Blog: Windows Store & Phone Developer Solutions
    My Blog: Http Client Protocol Issues (and other fun stuff I support)

    Friday, August 16, 2013 12:28 PM
    Moderator