Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ssands]

And you still think this is an MC problem?

It is almost certain to be an antivirus or security problem.

Except AV was completely uninstalled and Windows Defender was turned off. Firewall was turned off.
I think it has to do with a code change and a particular set of HW/SW on the computer. I've swapped out drivers to no effect.
The only change is the version of MC.
I've tried to eliminate every other variable. Even ran a HW check on my computer to see if there was a problem with any components.

[JimH]

You think it was uninstalled but it may not have been.   You may need to install Windows again or live with the problem.

[RoderickGI]

Well if Matt implements a hard kill to the thread if it keeps running, as he suggested here, then the problem may be solved in MC21.0.19 or MC21.0.20, or there abouts.

So not all hope is lost.

[JimH]

I think that's risky.  

And a kludge.  An ugly solution for someone else's problem.

[RoderickGI]

I think that's risky.  

And a kludge.  An ugly solution for someone else's problem.

Well actually I agree, and said so back here.

It is a pity there is no way, at least that I know of, to really identify what the issue is. I very rarely get any crashes with MC, but I did get one a couple of days ago, and it was related to Auto-Import. I was able to identify that MC was waiting for four internal threads, but as I use a normal (non-administrator) user on my HTPC, and didn't have Process Explorer available on it, I was unable to dig any further into what part of MC was causing the problem.

If anyone knows of better tools than those I have already mentioned, it would be great to hear about them. I suspect going any further than Task Manager, Resource Monitor, and Process Explorer, would get very technical.

[ssands]

Jim,

Is there anything I could do that would convince you that it might be a code issue and not a individual PC issue?

I've tried everything you have suggested (and more). Now, you are saying that I would need to reinstall Windows. But if I did that, with all the other AV and security-related caveats in place, and the problem remains, would you still dismiss this issue?

I've seriously considered that the problem is the PC and not MC and spent many hours trying to pinpoint the cause of the issue. (Because if it's my PC, I will get that addressed).

I agree that a fix that addresses a symptom and not the root cause can be risky (and I really do appreciate Matt for considering it, believe me).

So, I'm wondering what can be done to locate the root cause?

Matt has identified that the Auto-Import process is causing the hanging. If I keep everything the same and only change the MC version, it hangs. As I mentioned, I have done all the security/AV tests/uninstalls/etc. The core symptoms remain unchanged.

If you have diagnostics that I can run on this machine I will.

[lilyoliver]

Set up a test library with only local files.  If that works, then the NAS could be a problem.  If it doesn't work, then it probably isn't the NAS.

Unplug anything you can.  A bad USB drive, for example, could cause a problem.

Turn off auto import.

[ssands]

Set up a test library with only local files.  If that works, then the NAS could be a problem.  If it doesn't work, then it probably isn't the NAS.

Unplug anything you can.  A bad USB drive, for example, could cause a problem.

Turn off auto import.

Thanks. The issue was fixed in a subsequent dot release of the code. I recall some mention in release notes regarding it. No problems after that.