Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JS Engine : Memory leaks after 2 songs #693

Closed
SyncGit12 opened this issue Oct 26, 2024 · 11 comments
Closed

JS Engine : Memory leaks after 2 songs #693

SyncGit12 opened this issue Oct 26, 2024 · 11 comments
Labels
bug Something isn't working stale No recent comments/replies.

Comments

@SyncGit12
Copy link

Describe your bug here. If you are modding, try testing your bug in a clean version of the engine instead. Also, if you're using an older version of JSE, please try the latest version/action build. Also, be sure to check the pinned 'JS Engine: Known Issues' issue, to check if your issue hasn't already been found!

I was just debugging my mod and randomly it started leaking memory, Same on latest versions of the Engine

Command Prompt/Terminal/Crash logs (if existing)

No response

Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.

tutorial for da thing!!111!1!!!1111

steoep oen

loadsa a song

stwesrp twoe

sloasd antoeher song

boomhgo

mermeoy lekasks11!!11

Understandable version

Step 1,

Load a song

Step 2,

Load another song

boom

memory leaks

Are you modding a build from source or with Lua?

Source

What is your build target?

Windows

Did you edit anything in this build? If so, mention or summarize your changes.

working on mod

If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?

None

Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.

Yes

@SyncGit12 SyncGit12 added the bug Something isn't working label Oct 26, 2024
@StinkTheStinker
Copy link

what is your current amount of ram

@StinkTheStinker
Copy link

StinkTheStinker commented Oct 26, 2024

if you dont know how much ram you have, do ctrl+shift+esc, that will open task manager, then click on performance. it should show you the specs you have

@moxie-coder
Copy link
Collaborator

moxie-coder commented Oct 26, 2024

this engine has memory leaks unlike base psych tbh

@SyncGit12
Copy link
Author

that gave me an idea

spoiler alert:

nothin' engine will not have mem leaks

@SyncGit12
Copy link
Author

also my current amount of ram is 16 gb

@PatoFlamejanteTV
Copy link
Collaborator

bizarre

@SyncGit12
Copy link
Author

very bizzare for a 2017 computer that supports windows 11 restarts itself with force

@StinkTheStinker
Copy link

very bizzare for a 2017 computer that supports windows 11 restarts itself with force

well, that might be why

@SyncGit12
Copy link
Author

fool learn about computers and how they work, fucking idiot

@StinkTheStinker
Copy link

fool learn about computers and how they work, fucking idiot

how about you learn on how to not be a fucking bitch for 1 minute straight

fool

Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale No recent comments/replies. label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale No recent comments/replies.
Projects
None yet
Development

No branches or pull requests

4 participants