-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Azure Devops build: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. #4264
Comments
We need a Git Repository to check with, please provide some steps to reproduce as the exception is not enough for investigation |
i am of course not allowed to share oine of our repositories. it happens everytime we execute the given commands (see above) in each repository we use. it happens since yesterday when 6.0.3 was published and since the step is using 6.0.3 what more info do you need? |
As you can see from the stack trace, the problem occurs in LibGit2Sharp. The stack trace is: Which indicates that there's a commit with an author name so large it can't be unmarshalled from its native pointer into a C# @ulluoink, I would recommend that you go through the commits and inspect what author name may be the culprit here. Perhaps you can |
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. |
This issue was closed because it has been stalled for 30 days with no activity. Thank you for your contributions |
Prerequisites
GitVersion package
GitVersion.Tool
GitVersion version
6.0.3
Operating system
Windows
What are you seeing?
following exception is thrown every time Gitversion is executed.
the Exceptions began with version 6.0.3
What is expected?
should not throw exception and should work as expected ^^
Steps to Reproduce
dotnet tool install GitVersion.Tool --version 6.* --create-manifest-if-needed
dotnet tool restore
dotnet dotnet-gitversion /config $ConfigFilePath /output buildserver
RepositoryFixture Test
No response
Output log or link to your CI build (if appropriate).
No response
The text was updated successfully, but these errors were encountered: