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
When a project is created, we include a few default symbol servers.
This default selection is critical. Since it can influence the quality of the stack traces we provide OOTB.
But the relevance of these symbol servers is important. Since we don't want to excessively hit them with unrelated traffic since if the symbol server is set to contain pdbs (say a Microsoft Symbol Server), we'll hit it for all pdbs when stack walking.
For example, the default selection for a project, doesn't include NVIDIA:
But we get processing errors on events:
By default we could include it in some project types. For example. Unreal and Unity include PC games.
Is there a reason why we don't add the NVIDIA symbol server by default?
If so, when there's such processing error, we could at least have a suggestion: "Considering adding custom symbol servers. Click here to add NVIDIA".
The text was updated successfully, but these errors were encountered:
When a project is created, we include a few default symbol servers.
This default selection is critical. Since it can influence the quality of the stack traces we provide OOTB.
But the relevance of these symbol servers is important. Since we don't want to excessively hit them with unrelated traffic since if the symbol server is set to contain
pdbs
(say a Microsoft Symbol Server), we'll hit it for allpdbs
when stack walking.For example, the default selection for a project, doesn't include NVIDIA:

But we get processing errors on events:

By default we could include it in some project types. For example. Unreal and Unity include PC games.
Is there a reason why we don't add the NVIDIA symbol server by default?
If so, when there's such processing error, we could at least have a suggestion: "Considering adding custom symbol servers. Click here to add NVIDIA".
The text was updated successfully, but these errors were encountered: