Closed themida2000 closed 1 month ago
I cannot reproduce the behavior on my Windows or linux machine even when restricting it to 4 GB. Are you sure you systems resources are not used up by other software? JASP will require around 500 MB of RAM to load and edit your dataset (+150 MB per analysis). Could you provide the Memory usage per process (the three squares button in the left menu).
Hi @themida2000, It is quite strange, because your dataset is not big at all: 48 KB should be really easy to load. Can you load a dataset from the Data Library (Open/Data Library/1-Descriptives/Sleep for example)?
[image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] [image: image.png] Here I have included all the processes that consume memory. When I open JASP, I have only around 500 MB RAM left and when I close it it gets to 2 GB. Let me know if there is another software that interferes, but I haven't identified any.
Στις Τρί 21 Μαΐ 2024 στις 9:52 π.μ., ο/η RensDofferhoff < @.***> έγραψε:
I cannot reproduce the behavior on my Windows or linux machine even when restricting it to 4 GB. Are you sure you systems resources are not used up by other software? JASP will require around 500 MB of RAM to load and edit your dataset (+150 MB per analysis). Could you provide the Memory usage per process (the three squares button in the left menu).
— Reply to this email directly, view it on GitHub https://github.com/jasp-stats/jasp-issues/issues/2730#issuecomment-2121985784, or unsubscribe https://github.com/notifications/unsubscribe-auth/BITVWX5AAOHQBH4BZ7S4VQTZDL4MVAVCNFSM6AAAAABIABF3UCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRRHE4DKNZYGQ . You are receiving this because you authored the thread.Message ID: @.***>
Thx. You tried sending images via mail. That sadly does not work. Can you upload them directly on github issue-webpage? thx
Better look at the processes from down to up.
mmmh ... McAffee again. That one caused problems in the past. Can you disconect your PC from the internet and den disable McAffee for some minutes to see if that helps? If so, my personal advice would be to uninstall McAffee and use Microsoft Defender, which is included in Win 10 and 11 out of the box and is better in many cases. You just need to activate it after uninstalling McAffee. Also you could try closing Edge to free up some memory (RAM)
JASP is not using strange amounts of memory but there is very little RAM resources left on your pc.
@themida2000 Did some of our suggestions help?
You could also try this beta version: https://static.jasp-stats.org/Nightlies/Windows/JASP-nightly-development-eaf4ba837e4fa817ec87fd8acd11c52ab0e64739.msi
It helped removing the McAfee, because it freed up some memory space. But still for JASP to work without freezing, it needs to be opened with 50% RAM left and it then uses around 1,5- 2GB itself. So now I can use it, but I need to not open any other apps or open any internet windows. To free up more space I also fixed memory usage in Microsoft Edge. That helped also.
Thx for the feedback. You could also check if background apps like citrix, gamebar, lenovo vantage etc. are really needed always and disable that they autostart. And you could check if your laptop has a free RAM slot to upgrade its memory capacity. Other than that I am afraid that there is not much we can do. Big data sets and its analysis in JASP will always require quite some memory. So I am closing this one for now!
JASP Version
0.18.3
Commit ID
No response
JASP Module
Unrelated
What analysis are you seeing the problem on?
Edit data
What OS are you seeing the problem on?
Windows 11
Bug Description
I have quite a big dataset. 52 patients (rows) with around 80 variables each (columns). I am trying to edit the data but JASP is constantly freezing and 'Not responding'. Dataset ARCTIC.csv![image](https://github.com/jasp-stats/jasp-issues/assets/170351455/d6a9a02a-373b-4e30-b7a2-6ed8501792ee)
Expected Behaviour
Be able to edit data without any 'non responding' delays and freezing
Steps to Reproduce
...
Log (if any)
No response
Final Checklist