RUM-16604: Read process importance early by 0xnm · Pull Request #3504 · DataDog/dd-sdk-android

0xnm · 2026-06-03T13:14:34Z

What does this PR do?

In case of https://developer.android.com/topic/libraries/app-startup usage Datadog SDK may be started from the Content Provider.

And since we use process importance to start RUM pipeline

dd-sdk-android/features/dd-sdk-android-rum/src/main/kotlin/com/datadog/android/rum/internal/monitor/DatadogRumMonitor.kt

Lines 499 to 506 in e9efd7c

    
           override fun start() { 
        
               val processImportance = DdRumContentProvider.processImportance 
        
               val isAppInForeground = processImportance == 
        
                   ActivityManager.RunningAppProcessInfo.IMPORTANCE_FOREGROUND 
        
               handleEvent( 
        
                   RumRawEvent.SdkInit(isAppInForeground) 
        
               ) 
        
           }

and process importance is read in another Content Provider

dd-sdk-android/dd-sdk-android-internal/src/main/java/com/datadog/android/rum/DdRumContentProvider.kt

Lines 24 to 35 in e9efd7c

    
           override fun onCreate(): Boolean { 
        
               if (processImportance == 0) { 
        
                   val manager = context?.getSystemServiceAs<ActivityManager>(Context.ACTIVITY_SERVICE) 
        
                   val currentProcessId = Process.myPid() 
        
                   val currentProcess = manager?.runningAppProcesses?.firstOrNull { 
        
                       it.pid == currentProcessId 
        
                   } 
        
                   processImportance = currentProcess?.importance ?: DEFAULT_IMPORTANCE 
        
                   Log.w("DdRumContentProvider", "processImportance:$processImportance") 
        
               } 
        
               return true 
        
           }

we may have it not yet available by the time SDK starts, because it all depends on the initialization order.

This PR does the following:

assigns initOrder to the DdRumContentProvider, so it has a priority in the startup list
switches to getMyMemoryState API. It is available since API 16, so it is safe to use
to support rare cases when process importance is requested before DdRumContentProvider is initialized, we try to read it in the getter as well.

Review checklist (to be filled by reviewers)

Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
Make sure you discussed the feature or bugfix with the maintaining team in an Issue
Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

codecov-commenter · 2026-06-03T13:49:29Z

Codecov Report

❌ Patch coverage is 93.33333% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 72.14%. Comparing base (e9efd7c) to head (f11df77).

Files with missing lines	Patch %	Lines
...va/com/datadog/android/rum/DdRumContentProvider.kt	93.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3504      +/-   ##
===========================================
- Coverage    72.22%   72.14%   -0.07%     
===========================================
  Files          965      965              
  Lines        35596    35602       +6     
  Branches      5935     5932       -3     
===========================================
- Hits         25706    25685      -21     
- Misses        8278     8292      +14     
- Partials      1612     1625      +13

Files with missing lines	Coverage Δ
...va/com/datadog/android/rum/DdRumContentProvider.kt	`95.45% <93.33%> (+7.95%)`	⬆️

... and 36 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

0xnm marked this pull request as ready for review June 3, 2026 14:06

0xnm requested review from a team as code owners June 3, 2026 14:07

RUM-16604: Read process importance early

f11df77

0xnm force-pushed the nogorodnikov/rum-16604/read-process-importance-early branch from a4876d0 to f11df77 Compare June 3, 2026 14:54

ambushwork approved these changes Jun 3, 2026

View reviewed changes

0xnm merged commit 7720f9c into develop Jun 3, 2026
27 checks passed

0xnm deleted the nogorodnikov/rum-16604/read-process-importance-early branch June 3, 2026 15:49

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

RUM-16604: Read process importance early#3504

RUM-16604: Read process importance early#3504
0xnm merged 1 commit into
developfrom
nogorodnikov/rum-16604/read-process-importance-early

0xnm commented Jun 3, 2026

Uh oh!

codecov-commenter commented Jun 3, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	override fun start() {
	val processImportance = DdRumContentProvider.processImportance
	val isAppInForeground = processImportance ==
	ActivityManager.RunningAppProcessInfo.IMPORTANCE_FOREGROUND
	handleEvent(
	RumRawEvent.SdkInit(isAppInForeground)
	)
	}

	override fun onCreate(): Boolean {
	if (processImportance == 0) {
	val manager = context?.getSystemServiceAs<ActivityManager>(Context.ACTIVITY_SERVICE)
	val currentProcessId = Process.myPid()
	val currentProcess = manager?.runningAppProcesses?.firstOrNull {
	it.pid == currentProcessId
	}
	processImportance = currentProcess?.importance ?: DEFAULT_IMPORTANCE
	Log.w("DdRumContentProvider", "processImportance:$processImportance")
	}
	return true
	}

Uh oh!

Conversation

0xnm commented Jun 3, 2026

What does this PR do?

Review checklist (to be filled by reviewers)

Uh oh!

codecov-commenter commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

codecov-commenter commented Jun 3, 2026 •

edited

Loading