Resolved this issue just now.

I saw that the isar package I was using was holding an async write thread due to a deadlock formed because of 2 back to back writes to its cache.

To summarise, the actual culprit was a thread left running in the background, which made the entire debugger unresponsive.