Jump to content

Fixed!

Midnightisgone

By Midnightisgone,
in Second Life Viewer

 Share
You are about to reply to a thread that has been inactive for 1034 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Midnightisgone

Midnightisgone

Posted
Posted (edited)

I have uninstalled, cleared cache, lowered graphics, etc but I keep getting this error: 

 

Any help would be appreciated I keep getting kicked every 5 minutes :(

 

UPDATE: thank you to everyone who posted! Going to 64 instead of 32 seemed to work. I've been on for HOURS and haven't had a single error! 

340106c4cc6803ed8171ef62d15d8f56 (1).png

Edited by Midnightisgone
Link to comment
Share on other sites
Rowan Amore

Rowan Amore

Posted
Posted
  • Failed to allocate [xxxxxxx] bytes for LLVBOPool buffer [xxxx] error. This is an out of memory error. If you get this error frequently, things to try:
    • Lower your Draw Distance.
    • Close out other processes/programs not needed.
    • Close out browser tabs not needed or in use.
    • Reboot your PC to free up memory.
    • Open Preferences (Ctrl P) - Graphics - Hardware Settings - Enable OpenGL Vertex Buffer Objects - disable that setting. NB: This will result in a significant drop in FPS for some GPUs.
Link to comment
Share on other sites
Henri Beauchamp

Henri Beauchamp

Posted
Posted

Memory allocations failures may happen if:

  • You are using a 32 bits OS (time to upgrade, really...) or a 32 bits viewer on a 64 bits OS (this is totally silly: use the 64 bits viewer version !).
  • If, while using a 64 bits OS and a 64 bits viewer, you do not have enough RAM+swap space and are demanding too much to the viewer; e.g. setting a very high VRAM texture amount (keep in mind that the viewer will use about 1.5 times of RAM for textures as you what set for the VRAM), or draw distances beyond 256m in sims with neighbouring sims all around (such as in main land).

Not all viewers are created equal (mine is using less RAM and got many memory allocation failure checks and fallback code paths that prevent abrupt crashes), but all will fail at some point, when your system cannot cope with the amount of RAM they need due to the settings you are using.

Nowadays, 8Gb or RAM is pretty much a minimum, especially in complex rendering situations. 16Gb or more is recommended, if you want to push the settings upwards (especially the draw distance and the texture memory).

  • Like 1
Link to comment
Share on other sites
Nick0678

Nick0678

Posted
Posted (edited)

Like everyone said it looks like your system doesn't have enough RAM = you should buy more RAM.

But until you do that, there are a few tips which will help a bit with your current configuration.

 

Operating system:

Enable ZRam/Compcache (read your Operating system instructions/Community guidance on how to do that)

Enable/add more Swap (read your Operating system instructions/Community guidance on how to do that)

 

Firestorm:

Enable "Show friends only" to rez less avatars since those are the ones that usually consume too much RAM.

Enable "Restrict maximum texture resolution to 512px.." (Preferences> Graphics> Rendering)

DrgTKY6.png

Edited by Nick0678
  • Like 2
Link to comment
Share on other sites
Aishagain

Aishagain

Posted
Posted (edited)

@MidnightisgoneSomething that would help all the peer to peer support you are getting on this forum would be for you to post your system specifications here.

To do that go to the Help tab on the viewer interface and scroll down to "about Firestorm", copy that to your  clipboard and paste it in here.  You can edit out any personal detail, should you wish to.

Given that information, we can better understand your issue and probably advise you on a course of remedial  action. 🙂

Whirly has already asked you, I see, so I am merely emphasising the point!

Edited by Aishagain
Link to comment
Share on other sites
Midnightisgone

Midnightisgone

Posted
  • Author
Posted

Firestorm 6.4.21 (64531) Jul 21 2021 22:38:19 (32bit / SSE2) (Firestorm-Release) with Havok support
Release Notes

You are at 154.4, 151.3, 1,361.1 in Secrets located at simhost-0058957651c2251ee.agni
SLURL: http://maps.secondlife.com/secondlife/Secrets/154/151/1361
(global coordinates 109,466.0, 401,815.0, 1,361.1)
Second Life Server 2021-10-25.565008
Release Notes

CPU: Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz (2904 MHz)
Memory: 16309 MB
Concurrency: 12
OS Version: Microsoft Windows 8 64-bit (Build 9200)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
Graphics Card Memory: 6144 MB

Windows Graphics Driver Version: 30.0.14.9649
OpenGL Version: 4.6.0 NVIDIA 496.49

RestrainedLove API: (disabled)
libcurl Version: libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.8 nghttp2/1.40.0
J2C Decoder Version: KDU v8.1
Audio Driver Version: FMOD Studio 2.01.09
Dullahan: 1.8.0.202011211324
  CEF: 81.3.10+gb223419+chromium-81.0.4044.138
  Chromium: 81.0.4044.138
LibVLC Version: 2.2.8
Voice Server Version: Vivox 4.10.0000.32327

Settings mode: Firestorm
Viewer Skin: Firestorm (Grey)
Window size: 1920x1017 px
Font Used: Deja Vu (96 dpi)
Font Size Adjustment: 0 pt
UI Scaling: 1
Draw distance: 128 m
Bandwidth: 500 kbit/s
LOD factor: 2
Render quality: Medium (3/7)
Advanced Lighting Model: No
Texture memory: 512 MB (1)
Disk cache: Max size 2048.0 MB (97.1% used)
Built with MSVC version 1916
Packets Lost: 0/152,673 (0.0%)
December 01 2021 06:57:32 SLT

 

So sorry guys for whatever reason it wasn't notifying me about people posting. 

  • Thanks 1
Link to comment
Share on other sites
Midnightisgone

Midnightisgone

Posted
  • Author
Posted (edited)
5 minutes ago, Nick0678 said:

Your system is fine just use the 64bit version..

This happened on 64 bit as well :( This does happen however WAY more often when graphics are maximum, when I turn it down, np, but it still does it once in a while. 

Edited by Midnightisgone
Link to comment
Share on other sites
Nick0678

Nick0678

Posted
Posted
3 minutes ago, Midnightisgone said:

This happened on 64 bit as well :( This does happen however WAY more often when graphics are maximum, when I turn it down, np, but it still does it once in a while. 

Change to the 64bit version. 32bit applications cannot use more than 4GB of RAM so you are only making it worse.

  • Like 2
Link to comment
Share on other sites
You are about to reply to a thread that has been inactive for 1034 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...