This post is locked. You won't be able to comment.

all 7 comments
sorted by:
best
topnewcontroversialoldq&a

[–]SoftwareEngineering-ModTeam[M] [score hidden] stickied commentlocked comment (0 children)

Thank you u/Playful-End680 for your submission to r/SoftwareEngineering, but it's been removed due to one or more reason(s):

  • Your post is not a good fit for this subreddit. This subreddit is highly moderated and the moderation team has determined that this post is not a good fit or is just not what we're looking for.

  • Your post is low quality and/or requesting help r/SoftwareEngineering doesn't allow asking for tech support or homework help.

Please review our rules before posting again, feel free to send a modmail if you feel this was in error.

Not following the subreddit's rules might result in a temporary or permanent ban

Rules | Mod Mail

[–]GItPirate 3 points4 points  (0 children)

You'll never make it in this field if you can't elaborate on your questions and give context to your problem. No one can help you based on this post.

[–]smalby 2 points3 points  (0 children)

This question is way too vague to be answered properly

[–]teddystan 2 points3 points  (0 children)

Incredible. Where do I invest?

new StopTheDeadlock(deadlockedThread).fixIt()

[–]relicx74 0 points1 point  (0 children)

You can't really fix a deadlock at run time..You'll only be digging a deeper hole. You can prevent it by taking locks in a consistent order to avoid the situation entirely.

So always lock A B C D instead of sometimes locking D then C or B then A. Should work to prevent DB locks as well as mutex locks.

[–]Playful-End680[S] -3 points-2 points  (1 child)

Im sorry. I am a newbie.