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

memory-leak / corruption with large string assignments #559

Open
mdijkens opened this issue Oct 17, 2024 · 2 comments
Open

memory-leak / corruption with large string assignments #559

mdijkens opened this issue Oct 17, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@mdijkens
Copy link

Describe the bug
When (re)assigning a string variable with a large string (>1GB) after a few times program crashes

To Reproduce
Steps to reproduce the behavior:
c$=space$(1123123123)
c$=space$(1123123123)
c$=space$(1123123123)
c$=space$(1123123123)
c$=space$(1123123123)
c$=space$(1123123123)
c$=space$(1123123123)

Expected behavior
Program ends/continues normally

Screenshots
Program just aborts/killed

Desktop (please complete the following information):

  • OS: Windows 10
  • Version 3.14.1

Additional context
Ran into issue with c$=ReadFile$() reading multiple large files in a loop

@mdijkens mdijkens added the bug Something isn't working label Oct 17, 2024
@mdijkens
Copy link
Author

@mkilgore
Copy link
Contributor

The underlying issue is already reported here: #278

But note that due to how the string buffer is handled you'll need almost twice the total memory for the strings you create (so if you want to make 32GB of strings, you need around 64GB of total memory). Really, to be able to handle that much data the qbs string logic needs to be significantly improved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants