"The object has been rundown by the stub manager while there are external clients"

Question

"The object has been rundown by the stub manager while there are external clients"

Hong 1,246

await myStorageFolder.CreateFolderAsync("foo", CreationCollisionOption.OpenIfExists)

Why does the above code occasionally throw the following exception?

System.Exception: The object has been rundown by the stub manager while there are external clients.

I want to emphasize ”occasionally“. It usually works flawlessly. What does that error mean exactly? Could anyone shed some light on this?

Anonymous

2022-06-14T02:49:35.587+00:00

It's hard to say what's the reason for this issue. Could you reproduce this or get the log for this exception?

Hong 1,246

I am unable to reproduce it, unfortunately. It is logged in the app analytics.

What log did you refer to?

The stack trace:

System.Exception: The object has been rundown by the stub manager while there are external clients.  
  
The object has been rundown by the stub manager while there are external clients.  
  
 Stack Trace:  
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21  
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70  
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38  
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17  
   at Foo.App.<>c__DisplayClass51_1.<<GetStorageFolderByType>b__1>d.MoveNext() + 0xc2  
--- End of stack trace from previous location where exception was thrown ---  
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21  
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70  
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38  
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17  
   at ClassLibraryFoo.Utility.<RepeatTryAsync>d__139`1.MoveNext() + 0x11d

Anonymous

2022-06-15T06:59:14.043+00:00

Based on the log, the exception happens when the app is trying to get StorageFolder. I did some research about this, a possible scenario is that another process is using the Folder. My suggestion is that you might use the try/catch block to handle the exception and tell the customer to try again when the exception is thrown.

Accepted answer

1 additional answer

Your answer

Anonymous

2022-06-14T02:49:35.587+00:00

It's hard to say what's the reason for this issue. Could you reproduce this or get the log for this exception?
Hong 1,246 Reputation points

2022-06-14T14:02:54.84+00:00

I am unable to reproduce it, unfortunately. It is logged in the app analytics.

What log did you refer to?

The stack trace:

System.Exception: The object has been rundown by the stub manager while there are external clients. The object has been rundown by the stub manager while there are external clients. Stack Trace: at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17 at Foo.App.<>c__DisplayClass51_1.<<GetStorageFolderByType>b__1>d.MoveNext() + 0xc2 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17 at ClassLibraryFoo.Utility.<RepeatTryAsync>d__139`1.MoveNext() + 0x11d
Anonymous

2022-06-15T06:59:14.043+00:00

Based on the log, the exception happens when the app is trying to get StorageFolder. I did some research about this, a possible scenario is that another process is using the Folder. My suggestion is that you might use the try/catch block to handle the exception and tell the customer to try again when the exception is thrown.

Answer 1

Anonymous

Hello,

Welcome to Microsoft Q&A!

Based on the log, the exception happens when the app is trying to get StorageFolder. I did some research about this, a possible scenario is that another process is using the Folder. My suggestion is that you might use the try/catch block to handle the exception and tell the customer to try again when the exception is thrown.

Thank you.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Hong 1,246 Reputation points

2022-06-15T12:50:14.367+00:00

Thanks a lot. That is exactly the type of information that I was looking for. I just need a clue. Handling it is not a big deal because it happens rarely. Really hope Microsoft could make these exception messages more informative.
Could you turn your comment into an answer for me to accept?
Anonymous

2022-06-16T01:11:55.353+00:00

Sure, please kindly check my answer.

Answer 2

ELBANNOUNI.MOHAMMED 81

Les erreurs d’exécution peuvent se produire pour diverses raisons. Toutefois, toutes les erreurs ne doivent pas être gérées en tant qu’exceptions dans votre code.

Hong 1,246 Reputation points

2022-06-14T14:08:02.64+00:00

Thank you for the tip. This is not a serious problem because it happens only occasionally. The rate is well below 1%. I asked more out of curiosity than anything else.

Share via

"The object has been rundown by the stub manager while there are external clients"

1 additional answer

Your answer