Closed andremc420 closed 3 years ago
Ok, I just found the culprit: I unistalled TeraCopy and the issue is gone.
Hi,
Unfortunately, there isn't much for me to go on in the crash log. As I'm sure you know, the message on the fourth line (once unmangled) translates as 'Invalid window handle'. This is an error code (ERROR_INVALID_WINDOW_HANDLE
) which a Windows API function has probably returned, and foobar2000 has probably then turned it into an exception. (The error could mean that some window has just been closed or otherwise disappeared, although that could be foobar2000 itself.)
I can see an equivalent crash log has been submitted for foobar2000 1.5.1 and Columns UI 1.4.1, so I don't think there's any relation to newer versions of either of those.
I'm also unable to reproduce the problem after installing TeraCopy 3.8.5 in a Windows 10 VM. If you have more specific instructions (or a screen recording) I could try again.
Did you perhaps update to Windows 10 21H1 recently?
If it's happening when dragging from Windows Explorer to foobar2000, it may be related to TeraCopy's Windows Explorer integration (shell extensions).
Closed as this is resolved and there's nothing that can be acted on.
I recently upgraded foobar2000 to 1.6.7 and CuolumnsUI to the latest beta, but now if I try to drag a folder from Windows Explorer to foobar2000 it will crash instantly, even before I'm able to drop the items in the playlist.
I lready unisntalled and reinstalled foobar2000 and the issue persists with a fresh install.
If I start foobar2000 with Default User Interface it will work, so I'm sure it's an issue with ColumnsUI.
Here's the latest crash report: