-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
Large increase in memory use upon paste and delete operations in certain spreadsheets #433
Comments
Thanks for reporting this. This is interesting. It shows that maybe the undo feature is not handled at it should when altering extensive number of cells. |
I can add that at least from the user's perspective it does not only occur when copying multiple cells at once: In the attached spreadsheet, if one goes to H19, yy, j, Pc then it also increases memory usage quite a lot (around 800M). It seems less the number of cells being copied than how the computation is linked. In my sample spreadsheet, computation depends on another cell which in turn depends on another cell etc. It seems to me that this linking of the cell's computations somehow causes the large memory use. |
This froze my linux machine. |
@m7a made some changes. Please feel free to update to update to latest commit and try this again. Thanks. |
I can confirm that the issue is resolved in 66e87b0. Thank you very much for the fix! From my point of view, the issue can be closed :) . |
Thank you for your time and research. |
Hello,
I have found a memory-management issue but could not get my head around debugging it completely.
Here is how to reproduce it:
$ sc-im debugsc.sc
y
Pc
Expected: Program responds immediately
Note: When saving the changes and opening the changed file, memory use is down to 5 MiB again... until one attempts to delete the newly added cells. If doing this with visual select and then
x
, memory use will again increase to around 2 GiB...My local configuration (
~/.config/scimrc
) has this (but the problem seems to appear without anyscimrc
, too):Attachments
(does not exhibit excessive memory usage, thus it should not be the computation's problem)
(obtained through
valgrind --tool=massif --heap=yes --stacks=yes ./sc-im debugsc.sc
)System data:
I appreciate it very much if someone more knowledgeable of the source code could check this issue?
Thanks in advance
The text was updated successfully, but these errors were encountered: