Fix memory leaks

[YannisJustine]

Fixes #6715

Changes

• Implemented event callback cleanup on component unmounting
• Enhanced memory management through lifecycle hooks
• Maintained existing callbacks until full cleanup to preserve potential intentional behavior

Testing Methodology

1. Navigated through all component pages sequentially
2. Monitored memory usage patterns
3. Performed manual garbage collection after tests to ensure complete cleanup

Performance Impact

• Reduced memory footprint:
  Before:
  
  After:
  

Implementation Note

Chose to implement cleanup on unmount as a conservative approach since the requirements weren't explicit about element persistence. I kept the existing callbacks until they are all removed, as I wasn't sure if their accumulation was intentional. This ensures cleaner memory management while maintaining component integrity.

---

I hope this helps resolve the bug. I'm open to revising the PR based on your feedback and requirements.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments

Name	Status	Preview	Updated (UTC)
primevue	⬜️ Ignored (Inspect)	Visit Preview	Dec 11, 2024 7:40am
primevue-v3	⬜️ Ignored (Inspect)	Visit Preview	Dec 11, 2024 7:40am

[tugcekucukoglu]

Are _themesCallback and _configCallback sets necessary here?

[YannisJustine]

Are _themesCallback and _configCallback sets necessary here?

No, they're not necessary. I didn't know if the accumulation of callbacks was intentional or not.
I removed them in the last commit.