sasha-s/go-deadlock

Issues

• Wrong recursive locking detection with go 1.23

  #35 opened 4 months ago by philippseith
  0

• Support Go 1.23

  #34 opened 4 months ago by linkdata
  1

• Please add a new tag to provide TryLock function

  #33 opened 4 months ago by 578559967
  1

• Have you considered supporting TryLock?

  #28 opened a year ago by ly20119
  1

• panic in OnPotentialDeadlock callback

  #29 opened a year ago by atishaya11
  3

• Massive Memory Leak

  #26 opened 2 years ago by hubchub
  2

• Heads-up and suggestions for improvements

  #25 opened 2 years ago by linkdata
  1

• RLock 检查死锁存在问题: RWLock shouldn't check RLock order

  #4 opened 3 years ago by lycblank
  6

• Single thread lock in different order reported as deadlock

  #24 opened 3 years ago by yiminc
  2

• Bug in 1595213edefa28ca5047b00340c63557f9c051d0

  #19 opened 3 years ago by tsachiherman
  1

• Please tag a new release?

  #17 opened 3 years ago by jim-chou
  2

• document Opts to readme

  #21 opened 3 years ago by apmattil
  1

• Question: potential deadlock with goroutine stuck on internal lock?

  #15 opened 6 years ago by Thegaram
  6

• detect miss use of sync.Pool

  #16 opened 6 years ago by frostyplanet
  0

• Wrong deadlock detection in time.AfterFunc definitions

  #12 opened 6 years ago by ircop
  2

• the order of unlock in deadlock.go seems be strange

  #9 opened 7 years ago
  1

• RWLock shouldn't check RLock order

  #6 opened 7 years ago by smileusd
  2

• add deadlcok check of taking a lock twice in a goroutine

  #5 opened 7 years ago by smileusd
  1

• tests fail on linux/x86_64 with go 1.9

  #3 opened 7 years ago by decathorpe
  5

• Please tag this repository

  #1 opened 8 years ago by aviau
  1