Skip to content
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.

Empty string in CloudBlockBlob metadata causes CPU leak. #592

Closed
ansario opened this issue Dec 19, 2017 · 2 comments
Closed

Empty string in CloudBlockBlob metadata causes CPU leak. #592

ansario opened this issue Dec 19, 2017 · 2 comments

Comments

@ansario
Copy link

ansario commented Dec 19, 2017

The Azure Storage Rest API allows PUTing empty string values in the metadata of a CloudBlockBlob by setting the optional request header x-ms-meta-name to "". The C# nuget package (8.7.0) does not return when calling the .ListBlobs() method on a CloudBlobDirectory when one of the CloudBlockBlobs in the directory has a few, but not all, metadata values set to empty string. On each subsequent request, CPU increases by about 10%.

image001

Steps to reproduce:

  1. Create CloudBlockBlob with several metadata Keys + non empty string values via the REST API.
  2. Add one additional metadata key with an empty string value via the REST API.
  3. Using C# 8.7.0 nuget package, call .ListBlobs() on parent CloudBlobDirectory of the CloudBlockBlob.
  4. Observe CPU spike and infinte hang.
@kfarmer-msft
Copy link
Contributor

kfarmer-msft commented Oct 30, 2018

@ansario Does this still repro for you under 9.3.2 or 9.4.0? In particular, are you using sync or async APIs when you repro?

@seanmcc-msft
Copy link
Member

Duplicate of #828

@seanmcc-msft seanmcc-msft marked this as a duplicate of #828 Mar 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants