Repository navigation
GREF logging is broken in multi-process apps #1
Description
Scenario: Create a Xamarin.Android app, add a e.g. Service, and set ServiceAttribute.Process:
[Service(Process="example")]
public class MyService : Android.App.Service {
// ...
}
The problem is that the debug.mono.log system property is read at process startup -- for both (all) processes, the "normal" one and the "example" one, and they don't know to cooperate with each other.
The result is that they each write to grefs.txt, corrupting the contents.
Activity
[Xamarin.Android.Build.Tasks] Fragments & Shorter acw-map (#1301)
Squashed commit of the following:
[Java.Interop] Fix JNI reference count assertions
[Java.Runtime.Environment] Don't Destroy the JVM by default. (#65)
[Xamarin.Android.Build.Tasks] Emit an Error if a custom view cannot b…
[Xamarin.Android.Build.Tasks] Emit an Error if a custom view cannot b…
[Xamarin.Android.Build.Tasks] Emit an Error if a custom view cannot b…
[Xamarin.Android.Build.Tasks] Emit an Error if a custom view cannot b…
[Xamarin.Android.Build.Tasks] Emit an Error if a custom view cannot b…
[Xamarin.Android.Build.Tasks] Emit an Error if a custom view cannot b…
Fix ILRepack target on Linux
Fix ILRepack target on Linux
[Xamarin.Android.Build.Tasks] Fix ILRepack target rebuilds (#1979)
[Xamarin.Android.Build.Tasks] Emit an Error if a custom view cannot b…
50 remaining items
Prepare for new p/invoke code, step #1
Prepare for new p/invoke code, step #1
[Mono.Android] fix leaking lrefs in `TypeManager` (#9136)
[Xamarin.Android.Build.Tasks] Fix DSO name hash generation on Windows (…
[NativeAOT] fix default `SynchronizationContext` (#9883)
Call `MethodBase.Invoke(object, object[])`…
[native/mono] Use `mono_jit_thread_attach()` (#9937)
[tests] add a smoke test for `System.IO.Directory` (#10331)
[tests] add a smoke test for `System.IO.Directory` (#10331)
dotnet-policy-service commentedon May 8, 2026
We suspect this issue is stale and no longer relevant. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.
dotnet-policy-service commentedon May 22, 2026
This issue will now be closed since it had been marked "possibly-stale" but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.