Cool VL Viewer forum http://sldev.free.fr/forum/ |
|
Crashes with Memory Allication Failure http://sldev.free.fr/forum/viewtopic.php?f=6&t=2306 |
Page 1 of 4 |
Author: | DonFranko [ 2022-10-03 12:49:20 ] | ||
Post subject: | Crashes with Memory Allication Failure | ||
Hi Henri, since I use Zane's auto-derender script things got a lot better, but still I have big problems zooming when there are some people in a venue, sometimes I even crash when only a couple people are visibile for me. All of as sudden I get a Memory Allocatin Failure and then terrible crash that also effects the graphics settings of my pc (e.g. like the night light gets turned off) Attached you find the infos, hoping you can find the issue. Many thanks in advance!
|
Author: | Henri Beauchamp [ 2022-10-03 14:19:34 ] |
Post subject: | Re: Crashes with Memory Allication Failure |
Not an issue with the viewer itself, I'm afraid... If the OS reports a NULL pointer on a memory allocation request, all the viewer can do is report the problem to you and try and take conservatory measures (but the latter are limited, and some allocation failures cannot be trapped, causing crashes in the end). What you must find out is why the Hell your OS fails to allocate memory when there is still memory available to it ! Also, you should not be forced to derender avatars at all: I can attend venues with 80+ avatars and never run short of memory. Usual suspect are viruses/malware or... the anti-virus itself ! Try and use the task manager to detect the memory "eater". |
Author: | DonFranko [ 2022-10-03 17:00:07 ] | ||||
Post subject: | Re: Crashes with Memory Allication Failure | ||||
So, it's good to know that it's not the viewer , although that was quite clear as nobody else is complaining about Memory Allocation Crashes afaik. But as the crashes only happening with the viewer I thought of checking back with you. I attached a few screenshots of the CPU-Z app. Since some time I have a feeling that the problems occur because of that what you see at the screenshots. I have two Ram sticks and of em seems to be inconsistent with regards to the power Voltage. Could that be a reason to cause these kind of troubles when a lot more Ram than usually is used? and.. Does the log say OS or also about the GPU?
|
Author: | Henri Beauchamp [ 2022-10-03 18:19:00 ] |
Post subject: | Re: Crashes with Memory Allication Failure |
I see nothing wrong with the DDR settings, and should you have memory corruption issues, it won't translate in OS memory allocation failures but rather in random crashes... Again, try and use the Windows task manager to see what amount of memory the processes are consuming, and spot the culprit. |
Author: | Henri Beauchamp [ 2022-10-03 18:46:09 ] | ||||||||||||||||||||||||||||||||||||
Post subject: | Re: Crashes with Memory Allication Failure | ||||||||||||||||||||||||||||||||||||
Looking at the start of the log, I see weird issues that would hint for a corrupted viewer installation:
CONCLUSION: uninstall and reinstall the viewer... There are also strange settings, in your configuration:
Also, a factor (not visible in viewer logs) that could cause memory allocation failures under Windows would be the absence of any swap file (should you have manually set it to none)... For 16GB of RAM, Microsoft recommends a 4GB page file (=swap file). |
Author: | DonFranko [ 2022-10-03 22:49:14 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Post subject: | Re: Crashes with Memory Allication Failure | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: | DonFranko [ 2022-10-03 23:09:47 ] | ||||||||||||||||||
Post subject: | Re: Crashes with Memory Allication Failure | ||||||||||||||||||
|
Author: | Henri Beauchamp [ 2022-10-04 08:20:40 ] | ||||||||||||||||||||||||||||||||||||
Post subject: | Re: Crashes with Memory Allication Failure | ||||||||||||||||||||||||||||||||||||
If you want the viewer to be as mono-threaded as possible, you need to set the graphics driver (system-wide) setting for not multi-threading (meaning 30%-50% less fps); this is true for any viewer. For the Cool VL Viewer, you will also want to set the number of image decode threads (Preferences -> Cool features -> Misc) and GL worker threads (Preferences -> Graphics -> GPU/GL features) to (respectively) 1 and 0, which will degrade your rezzing experience... If I were you, I'd upgrade my PC with a better CPU (with 12 or 16 (real, not virtual/SMT) cores)... (1) The "kernel" is the OS "core" (main, central) software component. CPUs have hardware cores (true/genuine cores which may be seen as two virtual CPU cores when the CPU cores have SMT), not kernels. (2) From the Windows task manager (advanced/tabbed view), in the "Details" tab, right-click on the CoolVLViewer.exe process and choose "Set affinity" (or whatever is it called in English or your language), and uncheck all but one core (two (even and uneven consecutive ones) if you got SMT cores: e.g. cores 0 & 1). Proceed the same way with your sound software, affecting all other cores to it.
|
Author: | DonFranko [ 2022-10-04 09:06:45 ] | ||
Post subject: | Re: Crashes with Memory Allication Failure | ||
Thank you very much, Henri! I will have a look into all of that. Just right now after I've done the other changes I went to the lelutka shop, stayed there for a while and walked around looking.. then I flew back home where no traffic is.. then after 30 seconds crahsed and closed itself again. Would you mind having anouther look at the current log to maybe detect a reason for it?
|
Author: | Henri Beauchamp [ 2022-10-04 09:14:14 ] | |||||||||
Post subject: | Re: Crashes with Memory Allication Failure | |||||||||
|
Page 1 of 4 | All times are UTC |
Powered by phpBB® Forum Software © phpBB Group https://www.phpbb.com/ |