You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! Firstly, thank you for this very helpful library!
Secondly, I've noticed that after using pfd::open_file and selecting a file, debugger produces this message on Windows: onecore\com\combase\dcomrem\security.cxx(3071)\combase.dll!00007FFAAEFF9CFC: (caller: 00007FFA49E0823E) ReturnHr(1) tid(44c8) 80010117 Call context cannot be accessed after call completed.
Any thought on why this might happen? I've noticed that pfd::open_file, pfd::saveFile and pfd::select_folder produce this output. Just in case I've made a minimal example to reproduce this issue (don't forget to pull submodule).
I'm using Rider IDE for this which is using LLDB debugger and shows this output in "Debugger Output (LLDB)" tab.
I've also checked Visual Studio 2022 and it also has this issue (in "Output" tab).
Thank you in advance.
The text was updated successfully, but these errors were encountered:
Flone-dnb
changed the title
pfd::open_file produces weird debugger error
File dialog windows produce weird debugger output
Jun 20, 2022
Hello! Firstly, thank you for this very helpful library!
Secondly, I've noticed that after using
pfd::open_file
and selecting a file, debugger produces this message on Windows:onecore\com\combase\dcomrem\security.cxx(3071)\combase.dll!00007FFAAEFF9CFC: (caller: 00007FFA49E0823E) ReturnHr(1) tid(44c8) 80010117 Call context cannot be accessed after call completed.
Any thought on why this might happen? I've noticed that
pfd::open_file
,pfd::saveFile
andpfd::select_folder
produce this output. Just in case I've made a minimal example to reproduce this issue (don't forget to pull submodule).I'm using Rider IDE for this which is using LLDB debugger and shows this output in "Debugger Output (LLDB)" tab.
I've also checked Visual Studio 2022 and it also has this issue (in "Output" tab).
Thank you in advance.
The text was updated successfully, but these errors were encountered: