Resource Leak or Mismanagement

Please consider making a Pull Request if you are capable of doing so.

App Version:
2025.1.3

Affected Device(s):
Google Pixel with Android 11.0

Describe the bug:
Our team is developing a tool that can automatically identify potential resource issues in Android applications.

To detect resource anomalies, we designed five neutral cycles—GUI event sequences that should not increase resource usage:

① DOC (Double Orientation Change)
② Home (Return to Home Screen → Resume AUT)
③ Notification (Open Notification Bar → Close Notification Bar)
④ Text (Input Text → Clear Text)
⑤ Scroll (Swipe Down/Right → Swipe Up/Left)

The first three cycles are designed to trigger 3 main pairs of lifecycle callback functions (i.e., onCreate() and onDestroy(), onStart()/onRestart() and onStop(), onResume() and onPause()), while cycles ④ and ⑤ are based on UI interaction semantics, covering user input and scrolling scenarios that may also affect resource usage.

If executing a specific neutral cycle 50 times in a given state leads to continuous growth in certain resource metrics, we regard it as a potential resource leak or mismanagement issue that may cause software aging.

The bugs that have been successfully reproduced are uploaded here.
Material Files.zip

Each bug corresponds to one screenshot (A)—the image shows the page where the issue occurs.
Other information is encoded in the image filename as follows:

{ActivityName (B)}_{ExecutedNeutralCycle (C)}_{ResourcesWithContinuousGrowth (D)}

There may be some inaccuracies in state recognition, which could lead to duplicate reports. We apologize for any inconvenience this may cause.

We would greatly appreciate it if the developers could help us verify whether these issues truly exist. Your timely confirmation would be extremely valuable to our research and development efforts.

To Reproduce:
Steps to reproduce the behavior:

1. Open the Android app under test.
2. Execute the specified neutral cycle (based on C) 50 times in the indicated activity/state (based on A & B).
3. Observe the monitored resource metrics (based on D).
4. Identify whether any metric shows continuous growth.

Expected behavior:
Neutral cycles should not cause resource metrics to continuously increase.

Start by examining Material Files.zip and the screenshot filenames to identify the affected activity, neutral cycle, and resource metric. Reproduce the reported cycle 50 times on a Google Pixel running Android 11.0 with app version 2025.1.3, then compare the monitored metrics. Done means confirming whether the reported growth is a genuine leak or mismanagement issue.