Infinite recursion during resource lookup within System.Private.CoreLib #72381
Labels
area-Meta
needs-author-action
An issue or pull request that requires more info or actions from the author.
tenet-reliability
Reliability/stability related issue (stress, load problems, etc.)
Comments
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsDescriptionCoreCLR Version: 6.0.622.26707 ConfigurationRegression?Other information
|
|
Thanks. In order to assess the problem we will need more information, including SDK versions and a minimal reproduction demonstrating the problem. |
eiriktsarpalis
added
the
needs-author-action
|
This issue has been marked |
|
@introspection3 this is possibly a bug in .NET 6 but much more likely to be a corrupted process, and we should eliminate that first. So a repro case would be ideal, or else a dump file. Also please try to repro on another machine, another install. Also if possible whether it reproed before .NET 6. Eg., #53833 - unresolved, needed dump. |
danmoseley
changed the title
|
Stepping back, why is NullReferenceException is thrown in the first place. There is a bug somewhere. Networking folks can suggest whether it's networking implementation or user code. |
|
The stack suggests this was thrown by |
|
Would there be value in improving the message, eg., < Infinite recursion during resource lookup within System.Private.CoreLib. This may be a bug in System.Private.CoreLib, or potentially . Resource name: Arg_NullReferenceException
> Infinite recursion during resource lookup within System.Private.CoreLib. Verify that the process state is not corrupted. This can also be caused by an incomplete or corrupt installation of .NET, or by a bug in code running in certain extensibility points such as assembly resolve events or CultureInfo names. Resource name: Arg_NullReferenceExceptionWe could add |
|
Tagging subscribers to this area: @dotnet/area-meta Issue DetailsDescriptionConfigurationRegression?Other information
|
|
Triage: 6.0 problem. Unlikely networking -- these kind of issues typically indicate bad installation. Changing to Meta area for further investigation/triage/routing. |
|
Hi, is there any information about when this issue will be fixed? May be useful: By the way, for me changing phone language to EN-US fixes this problem. I've seen some threads on StackOverflow with simillar issues on other languages |
|
@tarekgh Does anything stand out for you on this, especially given @KiristonK's comment that setting locale to @KiristonK what locale were you on before changing to |
|
@jeffhandley I had Also some workaround for me with locales was setting app locale to CultureInfo.CurrentUICulture = new CultureInfo("en-US", false);
CultureInfo.CurrentCulture = new CultureInfo("en-US", false);
CultureInfo.DefaultThreadCurrentCulture = new CultureInfo("en-US", false);
CultureInfo.DefaultThreadCurrentUICulture = new CultureInfo("en-US", false); |
I don't think the issue is related to cultures or resources at all. There is another severe problem that is hiding there. Even when using culture different than Do we have dump for such failure? What OS was running on? does it repro on other machines/devices? CC @jkotas |
Yes, we would need a full crash dump to diagnose this issue. @KiristonK Is it possible to share the crash dump with us somehow? You can either save the dump in debugger, or you can configure OS to collect the crash dump on all fatal errors https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps when running without debugger. Does you app has a lot of custom interop with native code? It is not unusual for crashes like this one to be caused by bugs in interop that lead to memory corruptions. |
jkotas
added
the
tenet-reliability
|
@jkotas As i said before, now i can't reproduse this problem. The project that i attached still have wierd Flyout behavior (items does not show in release config, problem in If issue will occur again, where should i write about it, at dotnet/runtime or dotnet/maui issues? |
Yes, that's quite possible.
For the " Infinite recursion during resource lookup" crash like the one at the top, it is better to start with dotnet/runtime. |
|
Hit in #67049 Stacktrace |
|
@rzikm The stacktrace that you have shared points to the problem with the PR #67049 at one point that was fixed before the PR got merged. The PR was optimizing The "infinite recursion during resource lookup" is generic symptom of the things going wrong and the process state being corrupted. If you see this error message, it is unlikely to be a duplicate of the problem tracked by this issue - open a new issue instead. |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Configuration
Regression?
Other information
The text was updated successfully, but these errors were encountered: