[LeakScope] 5 Android lifecycle/memory violations detected

[MuhammadTehamsibAliTashfeen]

LeakScope: Android Lifecycle & Memory Leak Violations

About this report: This issue was automatically generated by LeakScope, a static analysis tool for Android lifecycle violations and memory leaks built on the Soot framework. This is part of an ongoing academic research study targeting ICSE 2027. No immediate action is required — we would greatly appreciate your feedback on whether these findings are accurate.

Summary

LeakScope detected 5 potential issue(s) across 2 detector type(s):

Severity	Count
🔴 High	1
🟡 Medium	0
🟢 Low (improvement opportunity)	4

Detector	Count	Severity	Description
StateHolderLeak	1	🔴 High	Static field holds UI/Context reference across configuration changes
ViewBindingOpportunity	4	🟢 Low	Manual findViewById() calls — ViewBinding migration opportunity

---

Detailed Findings

🔴 StateHolderLeak

Static field holds UI/Context reference across configuration changes

Finding #1 — VideoFilesActivity

Potential State Holder Memory Leak Detected
Class: com.example.videoplayer.activities.VideoFilesActivity
Issue: Scenario 2: Static field 'videoFilesAdapter' of type 'com.example.videoplayer.adapters.VideoFilesAdapter' in Activity/Fragment is a custom object that may hold UI references. Static fields survive configuration changes.
Fix: Use ViewModel or SavedStateHandle to persist state across rotations.

🟢 ViewBindingOpportunity

Manual findViewById() calls — ViewBinding migration opportunity

Finding #2 — VideoPlayerActivity

View Binding Migration Opportunity
Class: com.example.videoplayer.activities.VideoPlayerActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initViews
  • findViewById in initView
… (truncated for brevity)

Finding #3 — MainActivity

View Binding Migration Opportunity
Class: com.example.videoplayer.activities.MainActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in onCreate
  • findViewById in onCreate
Benefits of View Binding:
- Eliminates boilerplate findViewById() calls
- Compile-time type safety for view references
- Reduced null pointer exceptions
- Cleaner, more maintainable code
Note: This is a code modernization suggestion, not a memory leak

Finding #4 — AllowAccessActivity

View Binding Migration Opportunity
Class: com.example.videoplayer.activities.AllowAccessActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in onCreate
Benefits of View Binding:
- Eliminates boilerplate findViewById() calls
- Compile-time type safety for view references
- Reduced null pointer exceptions
- Cleaner, more maintainable code
Note: This is a code modernization suggestion, not a memory leak

Finding #5 — VideoFilesActivity

View Binding Migration Opportunity
Class: com.example.videoplayer.activities.VideoFilesActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in onCreate
  • findViewById in onCreate
Benefits of View Binding:
- Eliminates boilerplate findViewById() calls
- Compile-time type safety for view references
- Reduced null pointer exceptions
- Cleaner, more maintainable code
Note: This is a code modernization suggestion, not a memory leak

---

How to respond to this issue:

• If a finding is a true positive: consider applying the recommended fix and closing this issue.
• If a finding is a false positive: please leave a comment explaining why — your feedback directly improves our research.
• If you have questions: reply here or open a discussion.

This report was generated by LeakScope as part of the ICSE 2027 research artifact. Tool analyzes compiled APKs using Soot static analysis on VideoPlayer.