AOSSIE-Org / AOSSIE-Org/Resonate-Website

Bug: GSAP timeline instances not cleaned up in useEffect memory leak in page.jsx

Open
#307 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
43
Forks
154
PR merge metrics
No merged PRs in 30d

Description

### 🐛 Describe the bug

**Description:**
```
In `app/page.jsx`, four GSAP timelines are created inside `useEffect`
but never killed in the cleanup function:

- `heroTl` (line 45)
- `techStackTl` (line 109)
- `aboutTl` (line 142)
- `downloadTl` (line 181)

The current cleanup only calls:
- `lenis.destroy()`
- `ScrollTrigger.getAll().forEach(t => t.kill())`

GSAP timelines hold references to DOM elements and tween objects
independently of ScrollTrigger. Without calling `.kill()`, these
accumulate on every remount causing a memory leak.

## Steps to Reproduce
1. Open app/page.jsx
2. Check the useEffect cleanup block (line 213)
3. Notice heroTl, techStackTl, aboutTl, downloadTl are never killed

## Proposed Fix
Add to the cleanup return block:
heroTl.kill();
techStackTl.kill();
aboutTl.kill();
downloadTl.kill();

Image

Image

## References
Related to #292 (Animation Lifecycle & Memory Safety Audit)

I'd like to work on this issue.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.