High CPU utilization and eventually a core dump

[kedasy]

Describe the bug When using LINK to a file where the file type is not configured in the "Match Files" pattern, node for VS Code on Linux core dumps over and over and takes a lot of CPU.

v1.10.4 of Comment Anchors v1.94.0 of VS Code

To Reproduce Steps to reproduce the behavior:

I added a LINK like the following in a java file.

// LINK[id=deleteRecord] src/js/api/mobile-api.js#deleteRecord

I also had the following link in a JavaScript file. The two links point to each other for quick navigation. I have many of these between java and TypeScript files and they work just fine.

// LINK[id=deleteRecord] src/com/company/ws/mobile/MobileRestImpl.java#deleteRecord

I'm running with Remote - SSH into a Linux VM. With the above links, and after opening the java file, I was seeing node run at over 100% and eventually would die and core dump. This would happen over and over until my disk space was gone within the VM.

What I figured out is that we had the Comment Anchors "Match Files" Workspace setting set to "{/*.ts,/.java}". As soon as I added **/.js, then it worked just fine. This was hard to track down though and wasn't obvious.

Expected behavior

I expected the LINK to work and not cause major performance issues on my environment. Even just keeping it a dead link would have been fine, but taking up a lot of CPU and core dumping was not what I was expecting.