- Joined
- Nov 11, 2010
- Messages
- 326
- Motherboard
- Arch Linux x86_64
- CPU
- I5 2410m
- Graphics
- Intel 3000 HD 6490m Amd
- Mac
- Classic Mac
- Mobile Phone
Lately i've got two possible ideas to find the cause of the problem.
We know that...
- 8Gb of ram cause more glitches.
- GE=Yes makes freeze occur less often.
Now, the user liposuction, if i remember correctly, installed the Kexts for SL as well as the EFI String and got it work without problem/crash/lines.
So, if you can post here to explain what you did, it could be helpful somehow.
I've also noticed that the lines occur when the size of used ram reaches 3/3.5 GBs, which would explain why with 4GB is difficult to get them.
It can be a coincidence, so i developed a simple program in C++ that allocate the chosen amount of MBs in Ram to test out this with many users.
if you enter a value > of your free ram the SO will use the phisical memory to allocate the bytes, so be careful. (SWAP).
In any case, this program is completely safe: Once it is closed, all the memory allocated will be freed (as any c++ program).
Source included.
We know that...
- 8Gb of ram cause more glitches.
- GE=Yes makes freeze occur less often.
Now, the user liposuction, if i remember correctly, installed the Kexts for SL as well as the EFI String and got it work without problem/crash/lines.
So, if you can post here to explain what you did, it could be helpful somehow.
I've also noticed that the lines occur when the size of used ram reaches 3/3.5 GBs, which would explain why with 4GB is difficult to get them.
It can be a coincidence, so i developed a simple program in C++ that allocate the chosen amount of MBs in Ram to test out this with many users.
if you enter a value > of your free ram the SO will use the phisical memory to allocate the bytes, so be careful. (SWAP).
In any case, this program is completely safe: Once it is closed, all the memory allocated will be freed (as any c++ program).
Source included.