locked
Exception CDownloader::CreateUnsecureDownloadRequest

    Question

  • In my dashboard I see that my Windows Store apps has some crashes resulting from CDownloader::CreateUnsecureDownloadRequest. Downloading the cab file from the dashboard and using WinDbg to analyse the dump, I don't see what is causing the crash (maybe because lack of experience with WinDbg). When I set the filter in the dashboard, I see that it is only related to ARM devices. The app doesn't use the internet (only ads from PubCenter), so I assume the error 'CreateUnsecureDownloadRequest' is not coming from my code. The app makes use of C#/XAML and a C++/DirectX component.

    Has anyone seen this error before, or can give me a hint where or how to look for a clue?

    Thanks

    Ronald

    Friday, April 25, 2014 3:30 PM

Answers

  • Hi Ronald,

    From the cab file named: d768df433aae_Crash_26307533.cab, here's the faulting callstack...It seems from the callstack that there was an attempt to load an image resource from the package location in the format of: ms-appx://..., ms-appdata://.... or ms-resource://.... From the dump file itself, I can't tell the arguments (format of the URL) since it is a mini-dump without full memory and the dump unfortunately does not tell who initiated the call....

    If this is an app package issue...does your app package have a lot of images and if so, would there be any chance that your app package does not include a particular image?

    If this is a Advertising SDK issue, I am not quite sure what image it is trying to load...

    0:006> dpS 0xe0b9c695e8 L13
     00007ffb`89e19f31 Windows_UI_Xaml!CDownloader::CreateUnsecureDownloadRequest+0x613f61
     00007ffb`8980825e Windows_UI_Xaml!CommonBrowserHost::UnsecureDownload+0x13e
     00007ffb`89807d0a Windows_UI_Xaml!CCoreServices::UnsecureDownloadFromSite+0xa2
     00007ffb`8980676d Windows_UI_Xaml!ImageCache::Download+0xbd
     00007ffb`8980669e Windows_UI_Xaml!ImageCache::ProcessDecodeRequests+0xa0
     00007ffb`89801e54 Windows_UI_Xaml!ImageTaskDispatcher::Execute+0xc0
     00007ffb`89809c2e Windows_UI_Xaml!CommonBrowserHost::ProcessExecuteMessage+0x3a
     00007ffb`89809dad Windows_UI_Xaml!CXcpDispatcher::WindowProc+0x1fd
     00007ffb`b48f2524 user32!UserCallWinProcCheckWow+0x140
     00007ffb`b48f2387 user32!DispatchMessageWorker+0x1a7
     00007ffb`a7e6146f Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessages+0x19f
     00007ffb`a7e615e8 Windows_UI!Windows::UI::Core::CDispatcher::ProcessEvents+0x8d
     00007ffb`8981b07a Windows_UI_Xaml!CJupiterWindow::RunCoreWindowMessageLoop+0x3a
     00007ffb`8981b02f Windows_UI_Xaml!DirectUI::DXamlCore::RunMessageLoop+0x53
     00007ffb`a988d2fc twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::Run+0x30
     00007ffb`a988d183 twinapi_appcore!<lambda_6bc8d2bce135998a691b582442914b11>::operator()+0x103
     00007ffb`b02d0c6b SHCore!_WrapperThreadProc+0x15f
     00007ffb`b58515dd kernel32!BaseThreadInitThunk+0xd
     00007ffb`b5b243d1 ntdll!RtlUserThreadStart+0x1d


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

    Monday, April 28, 2014 5:39 PM
    Moderator

All replies

  • Hard to tell without a full callstack, can you paste the callstack here? Btw, the dump files are just "triage" dumps, so they are not really helpful to perform the full analysis, but alteast you should be able to see where the request originates from.

    Can you share your dump file through OneDrive or Dropbox?


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

    Friday, April 25, 2014 9:16 PM
    Moderator
  • Prashant,

    Here is the cab file:

    https://onedrive.live.com/redir?resid=9A6F31F60861DD2C!7005&authkey=!ABuXHXQ3YyFKduk&ithint=file%2c.cab

    Here is the view of the dashboard, with a faded tooltip

    Btw: With PubCenter, I mean the Microsoft Advertising SDK for Windows 8.1

    Thanks

    Ronald


    Saturday, April 26, 2014 9:02 AM
  • Hi Ronald,

    From the cab file named: d768df433aae_Crash_26307533.cab, here's the faulting callstack...It seems from the callstack that there was an attempt to load an image resource from the package location in the format of: ms-appx://..., ms-appdata://.... or ms-resource://.... From the dump file itself, I can't tell the arguments (format of the URL) since it is a mini-dump without full memory and the dump unfortunately does not tell who initiated the call....

    If this is an app package issue...does your app package have a lot of images and if so, would there be any chance that your app package does not include a particular image?

    If this is a Advertising SDK issue, I am not quite sure what image it is trying to load...

    0:006> dpS 0xe0b9c695e8 L13
     00007ffb`89e19f31 Windows_UI_Xaml!CDownloader::CreateUnsecureDownloadRequest+0x613f61
     00007ffb`8980825e Windows_UI_Xaml!CommonBrowserHost::UnsecureDownload+0x13e
     00007ffb`89807d0a Windows_UI_Xaml!CCoreServices::UnsecureDownloadFromSite+0xa2
     00007ffb`8980676d Windows_UI_Xaml!ImageCache::Download+0xbd
     00007ffb`8980669e Windows_UI_Xaml!ImageCache::ProcessDecodeRequests+0xa0
     00007ffb`89801e54 Windows_UI_Xaml!ImageTaskDispatcher::Execute+0xc0
     00007ffb`89809c2e Windows_UI_Xaml!CommonBrowserHost::ProcessExecuteMessage+0x3a
     00007ffb`89809dad Windows_UI_Xaml!CXcpDispatcher::WindowProc+0x1fd
     00007ffb`b48f2524 user32!UserCallWinProcCheckWow+0x140
     00007ffb`b48f2387 user32!DispatchMessageWorker+0x1a7
     00007ffb`a7e6146f Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessages+0x19f
     00007ffb`a7e615e8 Windows_UI!Windows::UI::Core::CDispatcher::ProcessEvents+0x8d
     00007ffb`8981b07a Windows_UI_Xaml!CJupiterWindow::RunCoreWindowMessageLoop+0x3a
     00007ffb`8981b02f Windows_UI_Xaml!DirectUI::DXamlCore::RunMessageLoop+0x53
     00007ffb`a988d2fc twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::Run+0x30
     00007ffb`a988d183 twinapi_appcore!<lambda_6bc8d2bce135998a691b582442914b11>::operator()+0x103
     00007ffb`b02d0c6b SHCore!_WrapperThreadProc+0x15f
     00007ffb`b58515dd kernel32!BaseThreadInitThunk+0xd
     00007ffb`b5b243d1 ntdll!RtlUserThreadStart+0x1d


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

    Monday, April 28, 2014 5:39 PM
    Moderator
  • Prashant,

    Thanks for analyzing the cab file. I use quit a bit of images as the content of buttons. There are some images missing, but these should not make the app crash (at least that is what I would expect, and it doesn't on my development en test machines).

    I fixed the missing images, and hopefully it will reduce the crash numbers.

    Thanks

    Ronald

    Tuesday, April 29, 2014 1:38 PM
  • OK, thanks for the update. I would just advise to keep an eye for any additional dump files and then take it from that point...Good luck!

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

    Tuesday, April 29, 2014 9:10 PM
    Moderator