paket.processlock-ed paket sometimes crashes with StackOverflowException
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
I am using Paket 5.241.2
Our concurrent build sometimes crashes with StackOverflowException.
From logs:
Could not acquire lock to C:\p2p\paket-files\paket.processlock.
Access to the path 'C:\p2p\paket-files\paket.processlock' is denied.
Trials left: 13.
Process is terminated due to StackOverflowException.
Performance:
- Disk IO: 5 milliseconds
- Runtime: 2 seconds
Also from logs:
C:\p2p.paket\paket.targets(65,5): error MSB3073: The command ""C:\p2p.paket\paket.exe" restore --references-file "C:\p2p\Src\XXXXXXXXXX\paket.references"" exited with code -1073741571. [C:\p2p\Src\XXXXXX.csproj]
(this is an old non-sdx-style csproj file)
This started happening when I upgraded from 5.176.6 to 5.241.2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Paket's paket.processlock acquisition and retry path, then compare behavior between versions 5.176.6 and 5.241.2. Reproduce the concurrent restore using the old non-sdx-style .csproj described in the report; done means lock contention no longer causes a StackOverflowException.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100