You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While downloading using DownloadBuildArtifacts@1 task it seems to download to memory. That task in turn just calls the DownloadBuildArtifactTaskV1_0_0 plugin located in this repo, hence it's being placed here.
What has been observed is that when downloading a larger file, in our case ~450MB, is that the agent memory usage increases by the download progression exactly and then freezes when it can no longer allocate more memory as those agents only have 1GB of RAM in total. Thus my conclusion is that the code downloads the artifact to memory instead of onto disk.
Versions
Current agent version: '3.245.0' / Debian 12
Environment type (Please select at least one enviroment where you face this issue)
Self-Hosted
Microsoft Hosted
VMSS Pool
Container
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
No response
Version controll system
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
What happened?
While downloading using
DownloadBuildArtifacts@1
task it seems to download to memory. That task in turn just calls the DownloadBuildArtifactTaskV1_0_0 plugin located in this repo, hence it's being placed here.What has been observed is that when downloading a larger file, in our case ~450MB, is that the agent memory usage increases by the download progression exactly and then freezes when it can no longer allocate more memory as those agents only have 1GB of RAM in total. Thus my conclusion is that the code downloads the artifact to memory instead of onto disk.
Versions
Current agent version: '3.245.0' / Debian 12
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
No response
Version controll system
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: