[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 1 detector type(s):

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

Detector	Count	Severity	Description
ViewBindingOpportunity	5	🟢 Low	Manual findViewById() calls — ViewBinding migration opportunity

---

Detailed Findings

🟢 ViewBindingOpportunity

Manual findViewById() calls — ViewBinding migration opportunity

Finding #1 — LoginActivity

View Binding Migration Opportunity
Class: be.kuleuven.findaset.activities.LoginActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in onBtnEnter_Clicked
  • findViewById in onBtnEnter_Clicked
  • 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 #2 — LeaderBoardActivity

View Binding Migration Opportunity
Class: be.kuleuven.findaset.activities.LeaderBoardActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in setConstraintGravity
  • findViewById in showDialog
  • findViewById in showDialog
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • 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 #3 — MainActivity

View Binding Migration Opportunity
Class: be.kuleuven.findaset.activities.MainActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in notifyWinDialog
  • findViewById in notifyWinDialog
  • findViewById in showDialog
  • findViewById in showDialog
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
  • findViewById in onCreate
Benefits of View
… (truncated for brevity)

Finding #4 — WelcomeActivity

View Binding Migration Opportunity
Class: be.kuleuven.findaset.activities.WelcomeActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in readCredentials
  • findViewById in readCredentials
  • findViewById in readCredentials
  • findViewById in showInfoDialog
  • findViewById in showInfoDialog
  • findViewById in onCreate
  • 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 #5 — RegisterActivity

View Binding Migration Opportunity
Class: be.kuleuven.findaset.activities.RegisterActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in onBtnRegister_Clicked
  • findViewById in onBtnRegister_Clicked
  • findViewById in onBtnRegister_Clicked
  • 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 FindASet.