NullReferenceException in SignalR's DefaultHubDispatcher #25612

Activity

1. javiercn

   added

   area-signalrIncludes: SignalR clients and serversIncludes: SignalR clients and servers

   on Sep 4, 2020
2. BrennanConroy commented on Sep 4, 2020

   

   BrennanConroy

   on Sep 4, 2020

   Last edited by BrennanConroy

   Member

   More actions

   I'm guessing your app is being shutdown ungracefully? If so, we can't really guarantee cleanup to be clean either.

   We can do a little cleanup here and move the CreateScope call outside of the try catch so the original exception is preserved.

   If you have a long running hub method that isn't observing connection close's (when the app shuts down) then that could cause this issue as well. Either using ApplicationStopping, or Context.ConnectionAborted.
3. BrennanConroy

   added this to the Backlog milestone on Sep 4, 2020
5. imb590 commented on Sep 7, 2020

   

   imb590

   on Sep 7, 2020

   Author

   More actions

   The shutdown is not graceful, but it is still reasonable to expect an exception from a disposed IServiceProvider in this case, not a NRE, isn't it?
6. davidfowl commented on Oct 2, 2020

   

   davidfowl

   on Oct 2, 2020

   Member

   More actions

   Yes absolutely it just makes it a lower priority.
7. BrennanConroy

   added

   affected-very-fewThis issue impacts very few customersThis issue impacts very few customers

   bugThis issue describes a behavior which is not expected - a bug.This issue describes a behavior which is not expected - a bug.

   severity-nice-to-haveThis label is used by an internal toolThis label is used by an internal tool

   on Nov 9, 2020
8. BrennanConroy

   closed this as completedin #29219on Feb 17, 2021
9. BrennanConroy

   modified the milestones: Backlog, 6.0-preview2 on Feb 17, 2021
10. ghost locked as resolved and limited conversation to collaborators on Mar 20, 2021