Mixing
UWP: Application Fault 1007 CStorageFileProxy release()
My UWP app (C# and XAML) uses Windows.Storage to open and save files (StorageFolder, StorageFile, FileIO, etc). Everything works for most of my users. However, I see a handful of crash reports listing the following title and stack trace. I'm unable to reproduce the error. A code review shows nothing, and internet searches turn up zero.
cstoragefileproxy release()
application_fault 00001007: application_fault
windows.storage.dll
CStorageFileProxy Release() dataaccess.cpp:3817
System.Private.Interop.dll
System::Runtime::InteropServices::McgMarshal ComRelease_StdCall() McgMarshal.cs:454
System.Private.Interop.dll
System::Runtime::InteropServices::McgMarshal ComRelease() McgMarshal.cs:473
System.Private.Interop.dll
System::__ComObject Cleanup() __ComObject.cs:903
System.Private.Interop.dll
System::RCWFinalizer Finalize() __ComObject.cs:58
mrt100_app.dll
System::Runtime::__Finalizer DrainQueue() __Finalizer.cs:61
mrt100_app.dll
System::Runtime::__Finalizer ProcessFinalizers() __Finalizer.cs:41
mrt100_app.dll
FinalizerStart() finalizerhelpers.cpp:69
ntdll.dll
RtlUserThreadStart() rtlstrt.c:1162
All of my code is C# and XAML, and there are no unsafe code blocks. I notice the "McgMarshal" entry in the stack trace, perhaps there's a thread issue.
Can anyone shed some light on what might cause Windows.Storage.DLL to fault given the above?
Thanks for any help!
c# uwp
asked Nov 20 '18 at 10:12
QubertQubert
196
add a comment |
My UWP app (C# and XAML) uses Windows.Storage to open and save files (StorageFolder, StorageFile, FileIO, etc). Everything works for most of my users. However, I see a handful of crash reports listing the following title and stack trace. I'm unable to reproduce the error. A code review shows nothing, and internet searches turn up zero.
cstoragefileproxy release()
application_fault 00001007: application_fault
windows.storage.dll
CStorageFileProxy Release() dataaccess.cpp:3817
System.Private.Interop.dll
System::Runtime::InteropServices::McgMarshal ComRelease_StdCall() McgMarshal.cs:454
System.Private.Interop.dll
System::Runtime::InteropServices::McgMarshal ComRelease() McgMarshal.cs:473
System.Private.Interop.dll
System::__ComObject Cleanup() __ComObject.cs:903
System.Private.Interop.dll
System::RCWFinalizer Finalize() __ComObject.cs:58
mrt100_app.dll
System::Runtime::__Finalizer DrainQueue() __Finalizer.cs:61
mrt100_app.dll
System::Runtime::__Finalizer ProcessFinalizers() __Finalizer.cs:41
mrt100_app.dll
FinalizerStart() finalizerhelpers.cpp:69
ntdll.dll
RtlUserThreadStart() rtlstrt.c:1162
All of my code is C# and XAML, and there are no unsafe code blocks. I notice the "McgMarshal" entry in the stack trace, perhaps there's a thread issue.
Can anyone shed some light on what might cause Windows.Storage.DLL to fault given the above?
Thanks for any help!
c# uwp
asked Nov 20 '18 at 10:12
QubertQubert
196
add a comment |
My UWP app (C# and XAML) uses Windows.Storage to open and save files (StorageFolder, StorageFile, FileIO, etc). Everything works for most of my users. However, I see a handful of crash reports listing the following title and stack trace. I'm unable to reproduce the error. A code review shows nothing, and internet searches turn up zero.
cstoragefileproxy release()
application_fault 00001007: application_fault
windows.storage.dll
CStorageFileProxy Release() dataaccess.cpp:3817
System.Private.Interop.dll
System::Runtime::InteropServices::McgMarshal ComRelease_StdCall() McgMarshal.cs:454
System.Private.Interop.dll
System::Runtime::InteropServices::McgMarshal ComRelease() McgMarshal.cs:473
System.Private.Interop.dll
System::__ComObject Cleanup() __ComObject.cs:903
System.Private.Interop.dll
System::RCWFinalizer Finalize() __ComObject.cs:58
mrt100_app.dll
System::Runtime::__Finalizer DrainQueue() __Finalizer.cs:61
mrt100_app.dll
System::Runtime::__Finalizer ProcessFinalizers() __Finalizer.cs:41
mrt100_app.dll
FinalizerStart() finalizerhelpers.cpp:69
ntdll.dll
RtlUserThreadStart() rtlstrt.c:1162
All of my code is C# and XAML, and there are no unsafe code blocks. I notice the "McgMarshal" entry in the stack trace, perhaps there's a thread issue.
Can anyone shed some light on what might cause Windows.Storage.DLL to fault given the above?
Thanks for any help!
c# uwp
asked Nov 20 '18 at 10:12
QubertQubert
196
My UWP app (C# and XAML) uses Windows.Storage to open and save files (StorageFolder, StorageFile, FileIO, etc). Everything works for most of my users. However, I see a handful of crash reports listing the following title and stack trace. I'm unable to reproduce the error. A code review shows nothing, and internet searches turn up zero.
cstoragefileproxy release()
application_fault 00001007: application_fault
windows.storage.dll
CStorageFileProxy Release() dataaccess.cpp:3817
System.Private.Interop.dll
System::Runtime::InteropServices::McgMarshal ComRelease_StdCall() McgMarshal.cs:454
System.Private.Interop.dll
System::Runtime::InteropServices::McgMarshal ComRelease() McgMarshal.cs:473
System.Private.Interop.dll
System::__ComObject Cleanup() __ComObject.cs:903
System.Private.Interop.dll
System::RCWFinalizer Finalize() __ComObject.cs:58
mrt100_app.dll
System::Runtime::__Finalizer DrainQueue() __Finalizer.cs:61
mrt100_app.dll
System::Runtime::__Finalizer ProcessFinalizers() __Finalizer.cs:41
mrt100_app.dll
FinalizerStart() finalizerhelpers.cpp:69
ntdll.dll
RtlUserThreadStart() rtlstrt.c:1162
All of my code is C# and XAML, and there are no unsafe code blocks. I notice the "McgMarshal" entry in the stack trace, perhaps there's a thread issue.
Can anyone shed some light on what might cause Windows.Storage.DLL to fault given the above?
Thanks for any help!
c# uwp
c# uwp
asked Nov 20 '18 at 10:12
QubertQubert
196
asked Nov 20 '18 at 10:12
QubertQubert
196
asked Nov 20 '18 at 10:12
QubertQubert
196
asked Nov 20 '18 at 10:12
QubertQubert
196
asked Nov 20 '18 at 10:12
QubertQubert
196
196
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Unfortunately after turning to .Net native compiler crash reports for UWP applications became mostly useless as you have found out. They need to be processed with .pdb files that you get while compiling the app to get the real actionable report. Microsoft promised to make tool that would do something like that, but for all those years it hasn't. I think I've seen someone on GitHub made some tool for that though it is far from friendly (works from the console), but I don't have a link for it.
answered Nov 20 '18 at 10:51
Ivan IčinIvan Ičin
3,84742343
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390700%2fuwp-application-fault-1007-cstoragefileproxy-release%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Unfortunately after turning to .Net native compiler crash reports for UWP applications became mostly useless as you have found out. They need to be processed with .pdb files that you get while compiling the app to get the real actionable report. Microsoft promised to make tool that would do something like that, but for all those years it hasn't. I think I've seen someone on GitHub made some tool for that though it is far from friendly (works from the console), but I don't have a link for it.
answered Nov 20 '18 at 10:51
Ivan IčinIvan Ičin
3,84742343
add a comment |
Unfortunately after turning to .Net native compiler crash reports for UWP applications became mostly useless as you have found out. They need to be processed with .pdb files that you get while compiling the app to get the real actionable report. Microsoft promised to make tool that would do something like that, but for all those years it hasn't. I think I've seen someone on GitHub made some tool for that though it is far from friendly (works from the console), but I don't have a link for it.
answered Nov 20 '18 at 10:51
Ivan IčinIvan Ičin
3,84742343
add a comment |
Unfortunately after turning to .Net native compiler crash reports for UWP applications became mostly useless as you have found out. They need to be processed with .pdb files that you get while compiling the app to get the real actionable report. Microsoft promised to make tool that would do something like that, but for all those years it hasn't. I think I've seen someone on GitHub made some tool for that though it is far from friendly (works from the console), but I don't have a link for it.
answered Nov 20 '18 at 10:51
Ivan IčinIvan Ičin
3,84742343
Unfortunately after turning to .Net native compiler crash reports for UWP applications became mostly useless as you have found out. They need to be processed with .pdb files that you get while compiling the app to get the real actionable report. Microsoft promised to make tool that would do something like that, but for all those years it hasn't. I think I've seen someone on GitHub made some tool for that though it is far from friendly (works from the console), but I don't have a link for it.
answered Nov 20 '18 at 10:51
Ivan IčinIvan Ičin
3,84742343
answered Nov 20 '18 at 10:51
Ivan IčinIvan Ičin
3,84742343
answered Nov 20 '18 at 10:51
Ivan IčinIvan Ičin
3,84742343
answered Nov 20 '18 at 10:51
Ivan IčinIvan Ičin
3,84742343
3,84742343
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390700%2fuwp-application-fault-1007-cstoragefileproxy-release%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
