Uploaded image for project: 'Firestorm'
  1. Firestorm
  2. FIRE-3967

[MAINT-693] newview/llappviewer.ccp(1619) : LLAppViwer :: mainLoop : Bad memory allocation in LLAppViewer :: mainLoop()!

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: Phoenix Firestorm 3.2.1, Phoenix Firestorm 3.2.2
    • Component/s: None
    • Labels:
    • Environment:
      Firestorm-3-2-1-24076 (NON OGL)
    • SL Avatar Name:
      Adama Thetan
    • Reported In:
      Firestorm 3.2.1.24076 QA

      Description

      EDIT (Whirly): https://jira.secondlife.com/browse/MAINT-693

      After a relog I keep getting >> ERROR MSG: --> newview/llappviewer.ccp(1619) : LLAppViwer :: mainLoop : Bad memory allocation in LLAppViewer :: mainLoop()!

      Firestorm-3-2-1-24076 (NON OGL)

      CPU: AMD Phenom(tm) II X4 955 Processor (3200.07 MHz)
      Memory: 8192 MB
      OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
      Graphics Card Vendor: NVIDIA Corporation
      Graphics Card: GeForce GTX 460/PCI/SSE2

      Windows Graphics Driver Version: 8.17.0012.8562
      OpenGL Version: 4.2.0

      1. 010912 Firestorm.log
        272 kB
        Fiona Classito
      2. 89b01c9b-2519-4c03-9812-3e1f5929d923.dmp
        0.0 kB
        Adama Thetan
      3. 90cf1759-c06b-418b-8abb-5ee817ab7641.dmp
        0.0 kB
        Jenova Spires
      4. AliceP27V5 Crash Logs SL Default Viewer.7z
        25 kB
        Saira Nitya Sunfire (AliceP27V% Resident)
      5. de6befeb-6a2e-4d53-87c0-130ecd274a38.dmp
        0.0 kB
        Jenova Spires
      6. debug_info.log
        18 kB
        Jenova Spires
      7. debug_info.log
        19 kB
        Adama Thetan
      8. Firestorm.log
        354 kB
        Saira Nitya Sunfire (AliceP27V% Resident)
      9. Firestorm.log
        124 kB
        Jenova Spires
      10. Firestorm.log
        122 kB
        Adama Thetan
      11. Firestorm.log
        148 kB
        Adama Thetan
      12. Firestorm.old
        116 kB
        Jenova Spires
      13. Firestorm01.log
        159 kB
        Adama Thetan
      14. Firestorm02.log
        159 kB
        Adama Thetan
      15. Firestorm03.log
        178 kB
        Adama Thetan
      16. Firestorm04.log
        110 kB
        Adama Thetan
      17. Firestorm05.log
        120 kB
        Adama Thetan
      18. Firestorm-Release_3_2_2_24336.exec_marker
        0.0 kB
        Jenova Spires
      19. static_debug_info.log
        16 kB
        Saira Nitya Sunfire (AliceP27V% Resident)
      20. stats.log
        1 kB
        Jenova Spires
      1. Firestorm Memory Error Pic 1.png
        6 kB

        Issue Links

          Activity

          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Hi Adama,

          Are you still seeing this particular error message on the 3.2.2 or 3.2.1 release builds?

          Show
          whirly.fizzle Whirly Fizzle added a comment - Hi Adama, Are you still seeing this particular error message on the 3.2.2 or 3.2.1 release builds?
          Hide
          rgelen Elrik Merlin added a comment - - edited

          I am noting something similar when crossing sim boundaries. However, the message I get from 3.2.2.24336 is SLIGHTLY different:

          ERROR: newviewer/llapviewer.cpp (1578):LLAppViewer::mainLoop:Bad memory allocation in LLAppViewer::mainLoop ()!

          The reporter of issue FIRE-4148 (closed as a duplicate of this one) notes the same error message as I get, with the same version number of the browser, so you currently have an additional user running 3.2.2.x who are getting this message but are not noted as experiencing the current bug.

          Show
          rgelen Elrik Merlin added a comment - - edited I am noting something similar when crossing sim boundaries. However, the message I get from 3.2.2.24336 is SLIGHTLY different: ERROR: newviewer/llapviewer.cpp (1578):LLAppViewer::mainLoop:Bad memory allocation in LLAppViewer::mainLoop ()! The reporter of issue FIRE-4148 (closed as a duplicate of this one) notes the same error message as I get, with the same version number of the browser, so you currently have an additional user running 3.2.2.x who are getting this message but are not noted as experiencing the current bug.
          Hide
          caeas@live.de Caeas added a comment -

          i have the problem since the release too.... mass crashes with this error

          Show
          caeas@live.de Caeas added a comment - i have the problem since the release too.... mass crashes with this error
          Hide
          karlhockey Karlhockey Forte added a comment -

          I am having this issue as well. Only happening on this release of Firestorm. Was only a few times it popped up, but it increased to not being able to use the client at all.

          CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (2400.03 MHz)
          Memory: 3071 MB
          OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
          Graphics Card Vendor: NVIDIA Corporation
          Graphics Card: GeForce 9800 GTX/9800 GTX+/PCI/SSE2
          Windows Graphics Driver Version: 6.14.0012.8558
          OpenGL Version: 3.3.0

          Show
          karlhockey Karlhockey Forte added a comment - I am having this issue as well. Only happening on this release of Firestorm. Was only a few times it popped up, but it increased to not being able to use the client at all. CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (2400.03 MHz) Memory: 3071 MB OS Version: Microsoft Windows XP Service Pack 3 (Build 2600) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 9800 GTX/9800 GTX+/PCI/SSE2 Windows Graphics Driver Version: 6.14.0012.8558 OpenGL Version: 3.3.0
          Hide
          apinkswan Stephanie Armstrong added a comment -

          I am having this issue as well now, but did not with FS Beta. I can't even count the number of times this happened to me last night.

          Show
          apinkswan Stephanie Armstrong added a comment - I am having this issue as well now, but did not with FS Beta. I can't even count the number of times this happened to me last night.
          Hide
          remi Remi Bohemian added a comment - - edited

          Edited: Also, I do not actually experience 1619 as an error message but instead 1578.
          Was told to comment here with my About Firestorm data because this is plaguing up to 3-5 times a night. I'm also usually only on 2-4 hours now, because this new Firestorm just, makes it impossible to stay extended periods. Interesting, it just happened right now when I tried to rebake my avatar. I did have available memory. Maybe not quadruple digits, but it's been enough for Firestorm to function in the past.

          Firestorm 3.2.2 (24336) Nov 27 2011 17:05:37 (Firestorm-Release)
          Release Notes

          You are at 220,319.0, 225,073.0, 2,526.4 in Ragnars Hamlet located at sim2542.agni.lindenlab.com (216.82.1.216:13000)
          Second Life Server 11.11.09.244706
          Retrieving...

          CPU: AMD Athlon(tm) 64 FX-51 Processor (2200 MHz)
          Memory: 2048 MB
          OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
          Graphics Card Vendor: NVIDIA Corporation
          Graphics Card: GeForce 6800 GT/AGP/SSE2/3DNOW!

          Windows Graphics Driver Version: 6.14.0012.8558
          OpenGL Version: 2.1.2
          RestrainedLove API: (disabled)
          libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
          J2C Decoder Version: KDU
          Audio Driver Version: FMOD version 3.750000
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Not Connected
          Settings mode: Phoenix
          Viewer Skin: firestorm (grey)
          Font Used: Deja Vu (96)
          Draw distance : 64
          Bandwidth : 1000
          LOD factor : 2
          Built with MSVC version 1600
          Packets Lost: 0/5,539 (0.0%)

          Show
          remi Remi Bohemian added a comment - - edited Edited: Also, I do not actually experience 1619 as an error message but instead 1578. Was told to comment here with my About Firestorm data because this is plaguing up to 3-5 times a night. I'm also usually only on 2-4 hours now, because this new Firestorm just, makes it impossible to stay extended periods. Interesting, it just happened right now when I tried to rebake my avatar. I did have available memory. Maybe not quadruple digits, but it's been enough for Firestorm to function in the past. Firestorm 3.2.2 (24336) Nov 27 2011 17:05:37 (Firestorm-Release) Release Notes You are at 220,319.0, 225,073.0, 2,526.4 in Ragnars Hamlet located at sim2542.agni.lindenlab.com (216.82.1.216:13000) Second Life Server 11.11.09.244706 Retrieving... CPU: AMD Athlon(tm) 64 FX-51 Processor (2200 MHz) Memory: 2048 MB OS Version: Microsoft Windows XP Service Pack 3 (Build 2600) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 6800 GT/AGP/SSE2/3DNOW! Windows Graphics Driver Version: 6.14.0012.8558 OpenGL Version: 2.1.2 RestrainedLove API: (disabled) libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1 J2C Decoder Version: KDU Audio Driver Version: FMOD version 3.750000 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Not Connected Settings mode: Phoenix Viewer Skin: firestorm (grey) Font Used: Deja Vu (96) Draw distance : 64 Bandwidth : 1000 LOD factor : 2 Built with MSVC version 1600 Packets Lost: 0/5,539 (0.0%)
          Hide
          aprille.shepherd Aprille Shepherd added a comment -

          I am on a Intel Vista 32 Bit Quad core with Nvidia 1 Gig card. We have all flavors of sims, but Brothel is a Magnum sim.
          I get Fatal Error 1578 Message many times each day. In older versions of Phoenix or FS, the error messages were not shown, but now i hope you may be able to see the source of the issue. It very often happens following the use of an external browser (surfing the net - I use Internat Explorer) or doing some sort of HTTP call (like sending group notices). We have a few HUDS that also do HTTP calls to a web site or SQL database and these seem to also bring about the same or similar result (crash). The viewer immediatly locks up. Music, voice and sounds continue. This can happen even after a fresh relog or after 12 hours online.
          However, if i do not use any HTTP calls i can stay on for at least 12 to 15 hours in a busy club (BROTHEL sim with traffic of over 30,000).
          It is my opinion that many many crashes in SL are tied to the use of External calls to HTTP. The viewer simply loses its place (and its mind). People hardly realize they are doing it. They open a web browser to look up something and close it, then go back to SL and...BOOM, they crash. I can make it happen pretty much on demand, so i try to use another computer to do web surfing and other stuff. Sucks if you want to copy and paste...sending links and text through IM from one Avi to another can get a bit tedious...but it saves a major crash.
          Can this be fixed???

          Show
          aprille.shepherd Aprille Shepherd added a comment - I am on a Intel Vista 32 Bit Quad core with Nvidia 1 Gig card. We have all flavors of sims, but Brothel is a Magnum sim. I get Fatal Error 1578 Message many times each day. In older versions of Phoenix or FS, the error messages were not shown, but now i hope you may be able to see the source of the issue. It very often happens following the use of an external browser (surfing the net - I use Internat Explorer) or doing some sort of HTTP call (like sending group notices). We have a few HUDS that also do HTTP calls to a web site or SQL database and these seem to also bring about the same or similar result (crash). The viewer immediatly locks up. Music, voice and sounds continue. This can happen even after a fresh relog or after 12 hours online. However, if i do not use any HTTP calls i can stay on for at least 12 to 15 hours in a busy club (BROTHEL sim with traffic of over 30,000). It is my opinion that many many crashes in SL are tied to the use of External calls to HTTP. The viewer simply loses its place (and its mind). People hardly realize they are doing it. They open a web browser to look up something and close it, then go back to SL and...BOOM, they crash. I can make it happen pretty much on demand, so i try to use another computer to do web surfing and other stuff. Sucks if you want to copy and paste...sending links and text through IM from one Avi to another can get a bit tedious...but it saves a major crash. Can this be fixed???
          Hide
          kool koolhoven Kool Koolhoven added a comment -

          I'm receiving several reports of the same error from people who isn't able to write in english or use JIRA.

          They use to get this error, in any circumstance (not necessarily crossing sim boundaries:

          ERROR: newview/llappviewer.cpp(1578) : LLAppViewer :: mainLoop: Bad Memory allocation in LLappViewer :: mainLoop ()!

          All of them use Windows, but I don't know if it's only a coincidence.

          Show
          kool koolhoven Kool Koolhoven added a comment - I'm receiving several reports of the same error from people who isn't able to write in english or use JIRA. They use to get this error, in any circumstance (not necessarily crossing sim boundaries: ERROR: newview/llappviewer.cpp(1578) : LLAppViewer :: mainLoop: Bad Memory allocation in LLappViewer :: mainLoop ()! All of them use Windows, but I don't know if it's only a coincidence.
          Hide
          dfairch Dick Fairchild added a comment -

          We have been receiving the same error message when trying to log in:

          Error: newview/llappviewer.cpp(1578) : LLAppViewer::mainloop: Bad memory allocation in LLAppViewer::mainloop()!

          Only happens with the current Firestorm. Phoenix is fine and the older Beta version of Firestorm was fine also. Just started occuring with the current Firestorm release.

          Show
          dfairch Dick Fairchild added a comment - We have been receiving the same error message when trying to log in: Error: newview/llappviewer.cpp(1578) : LLAppViewer::mainloop: Bad memory allocation in LLAppViewer::mainloop()! Only happens with the current Firestorm. Phoenix is fine and the older Beta version of Firestorm was fine also. Just started occuring with the current Firestorm release.
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          LL JIRA: https://jira.secondlife.com/browse/SH-2793
          This is fairly old, but just got moved to Shining & error message is the same.

          Suggestion from SH-2793:
          TEMPORARY WORKAROUND: Go to Preferences > Graphics tab > "Hardware Options" to set the Texture Memory to be 256MB if the current number is above that. This should prevent the out-of-memory problem that leads to a crash.

          Show
          whirly.fizzle Whirly Fizzle added a comment - LL JIRA: https://jira.secondlife.com/browse/SH-2793 This is fairly old, but just got moved to Shining & error message is the same. Suggestion from SH-2793: TEMPORARY WORKAROUND: Go to Preferences > Graphics tab > "Hardware Options" to set the Texture Memory to be 256MB if the current number is above that. This should prevent the out-of-memory problem that leads to a crash.
          Hide
          richardputnam Richard Putnam added a comment -

          I am having the same problem when attempting to log in. I get all the way through the login 'progress bar' and sometimes get to see in world for a second or 2 but then crash with this error message. I have tried logging in to a couple of different places and I have cleared all my cache manually but still not getting in.

          Show
          richardputnam Richard Putnam added a comment - I am having the same problem when attempting to log in. I get all the way through the login 'progress bar' and sometimes get to see in world for a second or 2 but then crash with this error message. I have tried logging in to a couple of different places and I have cleared all my cache manually but still not getting in.
          Hide
          lyn.mimistrobell Lyn Mimistrobell added a comment -

          Previously got the LLImageBase error and the LLVertexbuffer; disabled HTTP Get and VBO. Now getting the LLAppViewer error and haven't found a way to prevent it. Reducing texture memory from 512 to 256 has had no effect; tried the build I got from Whirly but that too crashed with LLAppViewer.

          For some reason, memory management is screwed up in 3.2.x

          Tail of the logfile:
          2011-12-23T21:15:04Z INFO: llmessage/llavatarnamecache.cpp(589) : LLAvatarNameCache::eraseUnrefreshed: 75 cached avatar names
          2011-12-23T21:15:04Z INFO: newview/llappviewer.cpp(4501) : LLAppViewer::idle: Transmitting sessions stats
          2011-12-23T21:15:04Z INFO: newview/llviewerstats.cpp(851) : send_stats: Misc Stats: int_1: i13 int_2: i10
          2011-12-23T21:15:04Z INFO: newview/llviewerstats.cpp(852) : send_stats: Misc Stats: string_1: '1920' string_2: 'Texture Time: 763.27, Total Time: 2423.82'
          2011-12-23T21:15:04Z INFO: newview/llviewerstats.cpp(392) : LLViewerStats::addToMessage: STAT: Version: 0.0
          2011-12-23T21:15:04Z INFO: newview/llviewerstats.cpp(392) : LLViewerStats::addToMessage: STAT: Vertex Buffers Enabled: 0.0
          2011-12-23T21:15:04Z INFO: newview/llviewerstats.cpp(398) : LLViewerStats::addToMessage: STAT: AgentPositionSnaps: Mean = 1432.4; StdDev = 0.4; Count = 2
          2011-12-23T21:15:05Z INFO: newview/llviewerstats.cpp(694) : ViewerStatsResponder::result: ViewerStatsResponder::result
          2011-12-23T21:15:05Z INFO: newview/llviewerdisplay.cpp(200) : display_stats: FPS: 25.60
          2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(164) : LLMemory::logMemoryInfo: Current allocated physical memory(KB): 754652
          2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(165) : LLMemory::logMemoryInfo: Current allocated page size (KB): 716168
          2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(166) : LLMemory::logMemoryInfo: Current availabe physical memory(KB): 923069
          2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(167) : LLMemory::logMemoryInfo: Current max usable memory(KB): 1677721
          2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(169) : LLMemory::logMemoryInfo: — private pool information –
          2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(170) : LLMemory::logMemoryInfo: Total reserved (KB): 0
          2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(171) : LLMemory::logMemoryInfo: Total allocated (KB): 0
          2011-12-23T21:15:07Z newview/llappviewer.cpp(1578) : error
          2011-12-23T21:15:07Z ERROR: newview/llappviewer.cpp(1578) : LLAppViewer::mainLoop: Bad memory allocation in LLAppViewer::mainLoop()!

          WinXP 32 bit

          Show
          lyn.mimistrobell Lyn Mimistrobell added a comment - Previously got the LLImageBase error and the LLVertexbuffer; disabled HTTP Get and VBO. Now getting the LLAppViewer error and haven't found a way to prevent it. Reducing texture memory from 512 to 256 has had no effect; tried the build I got from Whirly but that too crashed with LLAppViewer. For some reason, memory management is screwed up in 3.2.x Tail of the logfile: 2011-12-23T21:15:04Z INFO: llmessage/llavatarnamecache.cpp(589) : LLAvatarNameCache::eraseUnrefreshed: 75 cached avatar names 2011-12-23T21:15:04Z INFO: newview/llappviewer.cpp(4501) : LLAppViewer::idle: Transmitting sessions stats 2011-12-23T21:15:04Z INFO: newview/llviewerstats.cpp(851) : send_stats: Misc Stats: int_1: i13 int_2: i10 2011-12-23T21:15:04Z INFO: newview/llviewerstats.cpp(852) : send_stats: Misc Stats: string_1: '1920' string_2: 'Texture Time: 763.27, Total Time: 2423.82' 2011-12-23T21:15:04Z INFO: newview/llviewerstats.cpp(392) : LLViewerStats::addToMessage: STAT: Version: 0.0 2011-12-23T21:15:04Z INFO: newview/llviewerstats.cpp(392) : LLViewerStats::addToMessage: STAT: Vertex Buffers Enabled: 0.0 2011-12-23T21:15:04Z INFO: newview/llviewerstats.cpp(398) : LLViewerStats::addToMessage: STAT: AgentPositionSnaps: Mean = 1432.4; StdDev = 0.4; Count = 2 2011-12-23T21:15:05Z INFO: newview/llviewerstats.cpp(694) : ViewerStatsResponder::result: ViewerStatsResponder::result 2011-12-23T21:15:05Z INFO: newview/llviewerdisplay.cpp(200) : display_stats: FPS: 25.60 2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(164) : LLMemory::logMemoryInfo: Current allocated physical memory(KB): 754652 2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(165) : LLMemory::logMemoryInfo: Current allocated page size (KB): 716168 2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(166) : LLMemory::logMemoryInfo: Current availabe physical memory(KB): 923069 2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(167) : LLMemory::logMemoryInfo: Current max usable memory(KB): 1677721 2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(169) : LLMemory::logMemoryInfo: — private pool information – 2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(170) : LLMemory::logMemoryInfo: Total reserved (KB): 0 2011-12-23T21:15:07Z INFO: llcommon/llmemory.cpp(171) : LLMemory::logMemoryInfo: Total allocated (KB): 0 2011-12-23T21:15:07Z newview/llappviewer.cpp(1578) : error 2011-12-23T21:15:07Z ERROR: newview/llappviewer.cpp(1578) : LLAppViewer::mainLoop: Bad memory allocation in LLAppViewer::mainLoop()! WinXP 32 bit
          Hide
          jenova.spires Jenova Spires added a comment -

          I'm getting a similar message that "Bad memory allocation in LLAppViewer", but mine usually says the error has to do with a getting or displaying a texture.

          My system info:

          Firestorm 3.2.2 (24336) Nov 27 2011 17:05:37 (Firestorm-Release)
          Release Notes

          You are at 127,154.0, 179,898.0, 24.7 in Titus Groan located at sim5626.agni.lindenlab.com (216.82.22.146:12035)
          Second Life Server 11.12.03.246118
          Retrieving...

          CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2310.48 MHz)
          Memory: 3326 MB
          OS Version: Microsoft Windows Vista 32-bit Service Pack 2 (Build 6002)
          Graphics Card Vendor: NVIDIA Corporation
          Graphics Card: GeForce 210/PCI/SSE2/3DNOW!

          Windows Graphics Driver Version: 8.17.0012.8562
          OpenGL Version: 3.3.0
          RestrainedLove API: (disabled)
          libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
          J2C Decoder Version: KDU
          Audio Driver Version: FMOD version 3.750000
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Vivox 2.1.3010.6270

          Settings mode: V3
          Viewer Skin: starlight (original_teal)
          Font Used: Deja Vu (96)
          Draw distance : 64
          Bandwidth : 10000
          LOD factor : 4
          Built with MSVC version 1600
          Packets Lost: 22/19,410 (0.1%)

          Show
          jenova.spires Jenova Spires added a comment - I'm getting a similar message that "Bad memory allocation in LLAppViewer", but mine usually says the error has to do with a getting or displaying a texture. My system info: Firestorm 3.2.2 (24336) Nov 27 2011 17:05:37 (Firestorm-Release) Release Notes You are at 127,154.0, 179,898.0, 24.7 in Titus Groan located at sim5626.agni.lindenlab.com (216.82.22.146:12035) Second Life Server 11.12.03.246118 Retrieving... CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2310.48 MHz) Memory: 3326 MB OS Version: Microsoft Windows Vista 32-bit Service Pack 2 (Build 6002) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 210/PCI/SSE2/3DNOW! Windows Graphics Driver Version: 8.17.0012.8562 OpenGL Version: 3.3.0 RestrainedLove API: (disabled) libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1 J2C Decoder Version: KDU Audio Driver Version: FMOD version 3.750000 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Vivox 2.1.3010.6270 Settings mode: V3 Viewer Skin: starlight (original_teal) Font Used: Deja Vu (96) Draw distance : 64 Bandwidth : 10000 LOD factor : 4 Built with MSVC version 1600 Packets Lost: 22/19,410 (0.1%)
          Hide
          jenova.spires Jenova Spires added a comment -

          I'm getting this too; just happened again, after clearing cache.

          ERROR:llrender/llvertexbuffer.cp(1441) : LLVertexBuffer::mapVertexBuffer: memory allocation for vertex data failed.

          And now I cannot remain inworld more than a few seconds; the error I'm now seeing is
          ERROR:llimage/llimage.cpp(244) : LLImageBase::getData: Bad memory allocation for the image buffer!

          Firestorm 3.2.2 (24336) Nov 27 2011 17:05:37 (Firestorm-Release)
          Release Notes

          You are at 255,221.0, 256,500.0, 41.0 in Bonifacio located at sim9854.agni.lindenlab.com (216.82.45.188:13007)
          Second Life RC BlueSteel 11.12.12.246583
          Retrieving...

          CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2310.48 MHz)
          Memory: 3326 MB
          OS Version: Microsoft Windows Vista 32-bit Service Pack 2 (Build 6002)
          Graphics Card Vendor: NVIDIA Corporation
          Graphics Card: GeForce 210/PCI/SSE2/3DNOW!

          Windows Graphics Driver Version: 8.17.0012.8562
          OpenGL Version: 3.3.0
          RestrainedLove API: (disabled)
          libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
          J2C Decoder Version: KDU
          Audio Driver Version: FMOD version 3.750000
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Vivox 2.1.3010.6270

          Settings mode: V3
          Viewer Skin: starlight (original_teal)
          Font Used: Deja Vu (96)
          Draw distance : 64
          Bandwidth : 10000
          LOD factor : 4
          Built with MSVC version 1600
          Packets Lost: 125/9,683 (1.3%)

          Show
          jenova.spires Jenova Spires added a comment - I'm getting this too; just happened again, after clearing cache. ERROR:llrender/llvertexbuffer.cp(1441) : LLVertexBuffer::mapVertexBuffer: memory allocation for vertex data failed. And now I cannot remain inworld more than a few seconds; the error I'm now seeing is ERROR:llimage/llimage.cpp(244) : LLImageBase::getData: Bad memory allocation for the image buffer! Firestorm 3.2.2 (24336) Nov 27 2011 17:05:37 (Firestorm-Release) Release Notes You are at 255,221.0, 256,500.0, 41.0 in Bonifacio located at sim9854.agni.lindenlab.com (216.82.45.188:13007) Second Life RC BlueSteel 11.12.12.246583 Retrieving... CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2310.48 MHz) Memory: 3326 MB OS Version: Microsoft Windows Vista 32-bit Service Pack 2 (Build 6002) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 210/PCI/SSE2/3DNOW! Windows Graphics Driver Version: 8.17.0012.8562 OpenGL Version: 3.3.0 RestrainedLove API: (disabled) libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1 J2C Decoder Version: KDU Audio Driver Version: FMOD version 3.750000 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Vivox 2.1.3010.6270 Settings mode: V3 Viewer Skin: starlight (original_teal) Font Used: Deja Vu (96) Draw distance : 64 Bandwidth : 10000 LOD factor : 4 Built with MSVC version 1600 Packets Lost: 125/9,683 (1.3%)
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Hi Jenova,

          For ERROR:llrender/llvertexbuffer.cp(1441) : LLVertexBuffer::mapVertexBuffer: memory allocation for vertex data failed, see FIRE-4068 & for ERROR:llimage/llimage.cpp(244) : LLImageBase::getData: Bad memory allocation for the image buffer! see FIRE-4034

          Show
          whirly.fizzle Whirly Fizzle added a comment - Hi Jenova, For ERROR:llrender/llvertexbuffer.cp(1441) : LLVertexBuffer::mapVertexBuffer: memory allocation for vertex data failed, see FIRE-4068 & for ERROR:llimage/llimage.cpp(244) : LLImageBase::getData: Bad memory allocation for the image buffer! see FIRE-4034
          Hide
          jenova.spires Jenova Spires added a comment -

          @Whirly Fizzle: Thanks for the info!! I've updated those issues with the info. from my crashes & environment.

          Show
          jenova.spires Jenova Spires added a comment - @Whirly Fizzle: Thanks for the info!! I've updated those issues with the info. from my crashes & environment.
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Excellent. Thanks Jenova.

          Show
          whirly.fizzle Whirly Fizzle added a comment - Excellent. Thanks Jenova.
          Hide
          rider415 Hans Muellers added a comment -

          receive notecard from Firestorm CreateRmSysmemSurface: ___g1NvRmAllocMemory64 failed 42

          Running Vista and using Firestorm 3.22

          also reveived notice from my computer:
          ERROR:Llimage//Llimage.cpp(244):LlimageBase::getDATA: Bad Memory allocation for image buffer.

          I hope this helps

          Show
          rider415 Hans Muellers added a comment - receive notecard from Firestorm CreateRmSysmemSurface: ___g1NvRmAllocMemory64 failed 42 Running Vista and using Firestorm 3.22 also reveived notice from my computer: ERROR:Llimage//Llimage.cpp(244):LlimageBase::getDATA: Bad Memory allocation for image buffer. I hope this helps
          Hide
          tblackadder thisbe blackadder added a comment -

          i also have received these errors and Firestorm v3.2.2.24336 crashes

          i run OS X (Snow Leopard 10.6.8) with Intel Core 2 Duo processor & NVIDIA GeForce 9400 graphics card

          Show
          tblackadder thisbe blackadder added a comment - i also have received these errors and Firestorm v3.2.2.24336 crashes i run OS X (Snow Leopard 10.6.8) with Intel Core 2 Duo processor & NVIDIA GeForce 9400 graphics card
          Hide
          mimi anna Amilianna added a comment -

          Using this same veiwer I have crashed a number of nine times but the weird thing is I have full wifi connection and its starting to irritate me oh well at least I can still shop.

          Show
          mimi anna Amilianna added a comment - Using this same veiwer I have crashed a number of nine times but the weird thing is I have full wifi connection and its starting to irritate me oh well at least I can still shop.
          Hide
          mimi anna Amilianna added a comment -

          Okay so this is exactly what is happening I open my Firestorm v3.c.2.24336 I sign in and then wait for it to load then I'm waiting for like five minutes it says it's creating the bridge then it shows the notifications while you were away pop up then it crashes I can't run a business if it keeps crashing on me like this I might have to kick it old school and use veiwerv2.

          Show
          mimi anna Amilianna added a comment - Okay so this is exactly what is happening I open my Firestorm v3.c.2.24336 I sign in and then wait for it to load then I'm waiting for like five minutes it says it's creating the bridge then it shows the notifications while you were away pop up then it crashes I can't run a business if it keeps crashing on me like this I might have to kick it old school and use veiwerv2.
          Hide
          fiona Fiona Classito added a comment -

          Two crashes today, two different "Bad memory allocation" messages. Using Firestorm 3.2.2.24336. Has been crashing on occasion. My crashes are never on login - but rather after I've been logged in for some time. Crashed earlier today while walking through a sim:

          "llimage/llimage.cpp (244) LLImageBase::getData: "bad memory allocation for the image buffer!".

          I saw some mention about RAM in that Jira at FIRE-4034, so was watching memory usage as I crashed again an hour later during a TP. It appeared only 65% of memory was in use at the time of the crash. This second crash had a different message, though:

          "ERROR: newview/llappview.cpp(1578) : LLAppViewer::mainLoop: Bad memory allocation in LLAppViewer::mainLoop()!"

          I just installed LL Viewer 1 yesterday to try to solve the problem with outside SLurl location-based linking from Firefox opening new Firestorm windows. It did fix that, but did it cause another problem? I never crashed this much on Beta-Mesh. I might try going back to that to see what happens.

          ENVIRONMENT:

          Firestorm 3.2.2 (24336) Nov 27 2011 17:05:37 (Firestorm-Release)
          Release Notes

          CPU: AMD Phenom(tm) 9550 Quad-Core Processor (2210.13 MHz)
          Memory: 3071 MB
          OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
          Graphics Card Vendor: NVIDIA Corporation
          Graphics Card: GeForce 9800 GT/PCI/SSE2/3DNOW!

          Windows Graphics Driver Version: 6.14.0012.8026
          OpenGL Version: 3.3.0
          RestrainedLove API: RLV v2.7.0 / RLVa v1.4.3a
          libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
          J2C Decoder Version: KDU
          Audio Driver Version: FMOD version 3.750000
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Not Connected
          Settings mode: Hybrid
          Viewer Skin: metaharper (modern)
          Font Used: Deja Vu (96)
          Draw distance : 128
          Bandwidth : 600
          LOD factor : 4
          Built with MSVC version 1600

          Show
          fiona Fiona Classito added a comment - Two crashes today, two different "Bad memory allocation" messages. Using Firestorm 3.2.2.24336. Has been crashing on occasion. My crashes are never on login - but rather after I've been logged in for some time. Crashed earlier today while walking through a sim: "llimage/llimage.cpp (244) LLImageBase::getData: "bad memory allocation for the image buffer!". I saw some mention about RAM in that Jira at FIRE-4034 , so was watching memory usage as I crashed again an hour later during a TP. It appeared only 65% of memory was in use at the time of the crash. This second crash had a different message, though: "ERROR: newview/llappview.cpp(1578) : LLAppViewer::mainLoop: Bad memory allocation in LLAppViewer::mainLoop()!" I just installed LL Viewer 1 yesterday to try to solve the problem with outside SLurl location-based linking from Firefox opening new Firestorm windows. It did fix that, but did it cause another problem? I never crashed this much on Beta-Mesh. I might try going back to that to see what happens. ENVIRONMENT: Firestorm 3.2.2 (24336) Nov 27 2011 17:05:37 (Firestorm-Release) Release Notes CPU: AMD Phenom(tm) 9550 Quad-Core Processor (2210.13 MHz) Memory: 3071 MB OS Version: Microsoft Windows XP Service Pack 3 (Build 2600) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 9800 GT/PCI/SSE2/3DNOW! Windows Graphics Driver Version: 6.14.0012.8026 OpenGL Version: 3.3.0 RestrainedLove API: RLV v2.7.0 / RLVa v1.4.3a libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1 J2C Decoder Version: KDU Audio Driver Version: FMOD version 3.750000 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Not Connected Settings mode: Hybrid Viewer Skin: metaharper (modern) Font Used: Deja Vu (96) Draw distance : 128 Bandwidth : 600 LOD factor : 4 Built with MSVC version 1600
          Hide
          haydin romano Haydin Romano added a comment -

          I too have been having the same error pop up on my pc several times even after clearing my cache, rebooting my pc, and even had it happen when trying to log into sl. Here's my viewer and system information:

          Firestorm 3.2.2 (24336) Nov 27 2011 17:05:37 (Firestorm-Release)

          CPU: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (3411.15 MHz)
          Memory: 12265 MB
          OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
          Graphics Card Vendor: NVIDIA Corporation
          Graphics Card: GeForce GTX 570/PCI/SSE2

          Windows Graphics Driver Version: 8.17.0012.8562
          OpenGL Version: 4.2.0
          RestrainedLove API: (disabled)
          libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
          J2C Decoder Version: KDU
          Audio Driver Version: FMOD version 3.750000
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Vivox 2.1.3010.6270

          Settings mode: Phoenix
          Viewer Skin: firestorm (grey)
          Font Used: Deja Vu (96)
          Draw distance : 512
          Bandwidth : 10000
          LOD factor : 8
          Built with MSVC version 1600

          Show
          haydin romano Haydin Romano added a comment - I too have been having the same error pop up on my pc several times even after clearing my cache, rebooting my pc, and even had it happen when trying to log into sl. Here's my viewer and system information: Firestorm 3.2.2 (24336) Nov 27 2011 17:05:37 (Firestorm-Release) CPU: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (3411.15 MHz) Memory: 12265 MB OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce GTX 570/PCI/SSE2 Windows Graphics Driver Version: 8.17.0012.8562 OpenGL Version: 4.2.0 RestrainedLove API: (disabled) libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1 J2C Decoder Version: KDU Audio Driver Version: FMOD version 3.750000 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Vivox 2.1.3010.6270 Settings mode: Phoenix Viewer Skin: firestorm (grey) Font Used: Deja Vu (96) Draw distance : 512 Bandwidth : 10000 LOD factor : 8 Built with MSVC version 1600
          Hide
          tastyred D J Roff added a comment -

          Same with me. When I bring up SL, the login screen that is supposed to appear simply says "Host Not Found", on a pink screen. And when opening the internal browser, the same thing happens. I'm forced to use my external browser, which is a pain.

          Show
          tastyred D J Roff added a comment - Same with me. When I bring up SL, the login screen that is supposed to appear simply says "Host Not Found", on a pink screen. And when opening the internal browser, the same thing happens. I'm forced to use my external browser, which is a pain.
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Those of you getting this crash at or just after login, can you try the following:

          From the login screen, use CTRL+ALT+D to being up the Debug menu at the top after Help.
          Debug -> Show debug settings -> UseHTTPInventory -> set to FALSE
          Close Firestorm, then relaunch & login.

          @DJ Roff

          • Avatar -> Preferences -> Network & cache -> Adjust proxy settings -> Make sure all "use proxy" options are unchecked
          • Go to Preferences → Network & Cache and ensure that the following are all enabled:

          Enable Plugins
          Enable cookies
          Enable Javascript

          • If this doesnt work, go to Preferences → Privacy and click on Clear History (top of the window). Then relog
          • If still no luck, then make sure that your anti-virus software hasn't flagged, and possibly deleted, SLPlugin.exe, which is required for search to work. Try disabling your anti-virus completely, then reinstalling Firestorm to a different folder. Once done, re-enable your anti-virus and make sure you set it to exclude SLPlugin.exe from being scanned.

          Please file a support issue here if your still having problems with the Host not found message.

          Show
          whirly.fizzle Whirly Fizzle added a comment - Those of you getting this crash at or just after login, can you try the following: From the login screen, use CTRL+ALT+D to being up the Debug menu at the top after Help. Debug -> Show debug settings -> UseHTTPInventory -> set to FALSE Close Firestorm, then relaunch & login. @DJ Roff Avatar -> Preferences -> Network & cache -> Adjust proxy settings -> Make sure all "use proxy" options are unchecked Go to Preferences → Network & Cache and ensure that the following are all enabled: Enable Plugins Enable cookies Enable Javascript If this doesnt work, go to Preferences → Privacy and click on Clear History (top of the window). Then relog If still no luck, then make sure that your anti-virus software hasn't flagged, and possibly deleted, SLPlugin.exe, which is required for search to work. Try disabling your anti-virus completely, then reinstalling Firestorm to a different folder. Once done, re-enable your anti-virus and make sure you set it to exclude SLPlugin.exe from being scanned. Please file a support issue here if your still having problems with the Host not found message.
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Pushing to 4.0.1 now 3.3 is released

          Show
          whirly.fizzle Whirly Fizzle added a comment - Pushing to 4.0.1 now 3.3 is released
          Hide
          pinktrainers@hotmail.com Jelly Cat added a comment - - edited

          Hi all, Gwen has asked me to add my logs to this page as i am having the same problem, it first happens roughly around 10mins after i log in and can happen up to four times an hour, i used to be on sl for around 4 hours in the evening, but dont stay after 4-5 crashes now as it gets tedious having to keep re-logging. Added my crash logs too, so they can be compared with the others. Original post is here http://jira.phoenixviewer.com/browse/SUP-8796

          Firestorm 3.3.0 (24880) Feb 6 2012 20:10:16 (Firestorm-Release)
          Release Notes

          CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2210.05 MHz)
          Memory: 2048 MB
          OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
          Graphics Card Vendor: NVIDIA Corporation
          Graphics Card: GeForce 9500 GT/PCI/SSE2/3DNOW!

          Windows Graphics Driver Version: 6.14.0012.7533
          OpenGL Version: 3.3.0
          RestrainedLove API: (disabled)
          libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
          J2C Decoder Version: KDU
          Audio Driver Version: FMOD version 3.750000
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Not Connected
          Settings mode: Phoenix
          Viewer Skin: firestorm (grey)
          Font Used: Deja Vu (96)
          Draw distance : 360
          Bandwidth : 500
          LOD factor : 9.3
          Built with MSVC version 1600

          Show
          pinktrainers@hotmail.com Jelly Cat added a comment - - edited Hi all, Gwen has asked me to add my logs to this page as i am having the same problem, it first happens roughly around 10mins after i log in and can happen up to four times an hour, i used to be on sl for around 4 hours in the evening, but dont stay after 4-5 crashes now as it gets tedious having to keep re-logging. Added my crash logs too, so they can be compared with the others. Original post is here http://jira.phoenixviewer.com/browse/SUP-8796 Firestorm 3.3.0 (24880) Feb 6 2012 20:10:16 (Firestorm-Release) Release Notes CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2210.05 MHz) Memory: 2048 MB OS Version: Microsoft Windows XP Service Pack 3 (Build 2600) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 9500 GT/PCI/SSE2/3DNOW! Windows Graphics Driver Version: 6.14.0012.7533 OpenGL Version: 3.3.0 RestrainedLove API: (disabled) libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1 J2C Decoder Version: KDU Audio Driver Version: FMOD version 3.750000 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Not Connected Settings mode: Phoenix Viewer Skin: firestorm (grey) Font Used: Deja Vu (96) Draw distance : 360 Bandwidth : 500 LOD factor : 9.3 Built with MSVC version 1600
          Hide
          anandasandgrain Ananda Sandgrain added a comment -

          I experience this crash-to-desktop regularly, and I wanted to add some info on when it happens. I have found a few interesting things.
          1. If my inventory is fully loaded, I will crash within 20-30 minutes of starting up the viewer. This happens faster if I have been moving my camera around to do things such as build or adjust appearance. Fully loaded my inventory has about 77,000 items.
          2. If I clear cache and do not use the inventory at all (i.e. it doesn't load) I find I can run for some hours without crashing.
          3. I examined the memory use in each situation. Typically I will crash when the viewer memory use approaches 1,200,000 K according to Windows Task Manager. But here's why it's so bad - with a clear cache, the viewer uses about 350,000 K to start with. But if my inventory is loaded, it starts off using about 950,000 K! This leaves too little memory left to play with as the leaks build up over time. I have to admit I'm baffled why the inventory needs to keep over half a gig of stuff in memory all by itself.

          My specs:
          Firestorm 3.3.0 (24880) Feb 6 2012 20:10:16 (Firestorm-Release)
          Release Notes

          CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (2400.05 MHz)
          Memory: 3070 MB
          OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
          Graphics Card Vendor: NVIDIA Corporation
          Graphics Card: GeForce GT 240/PCIe/SSE2

          Windows Graphics Driver Version: 6.14.0012.9610
          OpenGL Version: 3.3.0
          RestrainedLove API: RLV v2.7.0 / RLVa v1.4.3a
          libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
          J2C Decoder Version: KDU
          Audio Driver Version: FMOD version 3.750000
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Not Connected
          Settings mode: Phoenix
          Viewer Skin: firestorm (grey)
          Font Used: Deja Vu (96)
          Draw distance : 64
          Bandwidth : 1300
          LOD factor : 2
          Built with MSVC version 1600

          Show
          anandasandgrain Ananda Sandgrain added a comment - I experience this crash-to-desktop regularly, and I wanted to add some info on when it happens. I have found a few interesting things. 1. If my inventory is fully loaded, I will crash within 20-30 minutes of starting up the viewer. This happens faster if I have been moving my camera around to do things such as build or adjust appearance. Fully loaded my inventory has about 77,000 items. 2. If I clear cache and do not use the inventory at all (i.e. it doesn't load) I find I can run for some hours without crashing. 3. I examined the memory use in each situation. Typically I will crash when the viewer memory use approaches 1,200,000 K according to Windows Task Manager. But here's why it's so bad - with a clear cache, the viewer uses about 350,000 K to start with. But if my inventory is loaded, it starts off using about 950,000 K! This leaves too little memory left to play with as the leaks build up over time. I have to admit I'm baffled why the inventory needs to keep over half a gig of stuff in memory all by itself. My specs: Firestorm 3.3.0 (24880) Feb 6 2012 20:10:16 (Firestorm-Release) Release Notes CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (2400.05 MHz) Memory: 3070 MB OS Version: Microsoft Windows XP Service Pack 3 (Build 2600) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce GT 240/PCIe/SSE2 Windows Graphics Driver Version: 6.14.0012.9610 OpenGL Version: 3.3.0 RestrainedLove API: RLV v2.7.0 / RLVa v1.4.3a libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1 J2C Decoder Version: KDU Audio Driver Version: FMOD version 3.750000 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Not Connected Settings mode: Phoenix Viewer Skin: firestorm (grey) Font Used: Deja Vu (96) Draw distance : 64 Bandwidth : 1300 LOD factor : 2 Built with MSVC version 1600
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          @Jelly

          LOD factor : 9.3
          Yikes, that setting is really too high. Drop your LOD down to 3-4. This should help.

          @Ananda
          What you are seeing with memory use differences on a full & empty cache is to be expected & with a large inventory, it will make a noticebale difference. I see exactly the same as you, my inventory is 96k.
          Each item in your inventory takes up roughly 10kb of memory (i cant remember the exact figure, 7 ish kb I think, but use 10 for easy maths lol). So if you have a large, loaded inventory, in your case, thats at least 500Mb gone right there, just on inventory There is nothing you can do to change this, apart from box items up.
          If you have an alt with small inventory, you will also see how much less RAM the alt uses & so consqequently will have less out of memory crashes. Test with other viewers too, you will see the same behaviour.
          LL dont actually recommend inventory sizes over 10-12k (!!!) for stability reasons.

          Show
          whirly.fizzle Whirly Fizzle added a comment - @Jelly LOD factor : 9.3 Yikes, that setting is really too high. Drop your LOD down to 3-4. This should help. @Ananda What you are seeing with memory use differences on a full & empty cache is to be expected & with a large inventory, it will make a noticebale difference. I see exactly the same as you, my inventory is 96k. Each item in your inventory takes up roughly 10kb of memory (i cant remember the exact figure, 7 ish kb I think, but use 10 for easy maths lol). So if you have a large, loaded inventory, in your case, thats at least 500Mb gone right there, just on inventory There is nothing you can do to change this, apart from box items up. If you have an alt with small inventory, you will also see how much less RAM the alt uses & so consqequently will have less out of memory crashes. Test with other viewers too, you will see the same behaviour. LL dont actually recommend inventory sizes over 10-12k (!!!) for stability reasons.
          Hide
          satilumet Sati Lumet added a comment -

          I do have this when I am in the upload window , and try to aktivate Weight/joints in Preview
          maybe by a bad Collada file shrugs

          Show
          satilumet Sati Lumet added a comment - I do have this when I am in the upload window , and try to aktivate Weight/joints in Preview maybe by a bad Collada file shrugs
          Hide
          gabimarshdevil Gabriella Marshdevil added a comment -

          I'm having the same crash problems. My inventory is +54k
          Some days ago I log in my friend's account to take a snapshot for her, with shadows enabled, and I didnt' have any problem (and I took hours to take a snapshot, since I was experimenting with windlight settings). I also took snapshots in other sims while I was logged in my alt which had a 6k-7k inventory, I had no problems with this.

          ------------------------------------------------------------------------------------

          Firestorm 3.3.0 (24880) Feb 6 2012 20:10:16 (Firestorm-Release)[ReleaseNotes]

          Você está em 103.042,0, 401.973,0, 26,0 em Marathon Caye localizado em sim7776.agni.lindenlab.com(216.82.36.15:13001)
          Second Life Server 12.02.24.249991
          [Notas de versão [ReleaseNotes]]

          CPU: AMD Phenom(tm) II X4 850 Processor (3315.13 MHz)
          Memória: 2048 MBs
          Versão OS: Microsoft Windows 7 32-bit Service Pack 1 (Build 7601)
          Placa de vídeo: ATI Technologies Inc.
          Placa gráfica: ATI Radeon HD 4650

          Versão do driver de vídeo Windows: ATI Technologies Inc.
          Versão OpenGL: 3.3.11554 Compatibility Profile Context

          Viewer Skin: starlight (original_orange)
          RestrainedLove API: (disabled)
          Versão libcurl: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
          Versão J2C Decoder: KDU
          Versão do driver de áudio: FMOD version 3.750000
          Versão Qt Webkit: 4.7.1 (version number hard-coded)
          Versão do servidor de voz: Vivox 2.1.3010.6270

          Settings mode: Phoenix
          Viewer Skin: starlight (original_orange)
          Font Used: Deja Vu (96)
          Draw distance : 64
          Bandwidth : 500
          LOD factor : 2
          Construído com MSVC versão 1600
          Packets Lost: 1/8.195 (0,0%)

          Show
          gabimarshdevil Gabriella Marshdevil added a comment - I'm having the same crash problems. My inventory is +54k Some days ago I log in my friend's account to take a snapshot for her, with shadows enabled, and I didnt' have any problem (and I took hours to take a snapshot, since I was experimenting with windlight settings). I also took snapshots in other sims while I was logged in my alt which had a 6k-7k inventory, I had no problems with this. ------------------------------------------------------------------------------------ Firestorm 3.3.0 (24880) Feb 6 2012 20:10:16 (Firestorm-Release) [ReleaseNotes] Você está em 103.042,0, 401.973,0, 26,0 em Marathon Caye localizado em sim7776.agni.lindenlab.com(216.82.36.15:13001) Second Life Server 12.02.24.249991 [Notas de versão [ReleaseNotes] ] CPU: AMD Phenom(tm) II X4 850 Processor (3315.13 MHz) Memória: 2048 MBs Versão OS: Microsoft Windows 7 32-bit Service Pack 1 (Build 7601) Placa de vídeo: ATI Technologies Inc. Placa gráfica: ATI Radeon HD 4650 Versão do driver de vídeo Windows: ATI Technologies Inc. Versão OpenGL: 3.3.11554 Compatibility Profile Context Viewer Skin: starlight (original_orange) RestrainedLove API: (disabled) Versão libcurl: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1 Versão J2C Decoder: KDU Versão do driver de áudio: FMOD version 3.750000 Versão Qt Webkit: 4.7.1 (version number hard-coded) Versão do servidor de voz: Vivox 2.1.3010.6270 Settings mode: Phoenix Viewer Skin: starlight (original_orange) Font Used: Deja Vu (96) Draw distance : 64 Bandwidth : 500 LOD factor : 2 Construído com MSVC versão 1600 Packets Lost: 1/8.195 (0,0%)
          Hide
          hikaruashida Lerochelle Destiny added a comment -

          I keep getting this, or just crashing to desktop. As a result, I cannot build anything. Seems to happen most when building or manipulating prims.

          ****

          Firestorm 4.2.2 (29837) Aug 27 2012 19:20:05 (Firestorm-Release)
          Release Notes

          You are at 214,305.0, 252,606.0, 1,117.2 in Imagine Isla located at sim3241.agni.lindenlab.com (216.82.1.95:12035)
          Second Life RC Magnum 12.11.09.266804
          Release Notes

          CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (3093.02 MHz)
          Memory: 8174 MB
          OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
          Graphics Card Vendor: NVIDIA Corporation
          Graphics Card: GeForce GTX 550 Ti/PCIe/SSE2

          Windows Graphics Driver Version: 9.18.0013.0697
          OpenGL Version: 4.2.0

          RestrainedLove API: (disabled)
          libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
          J2C Decoder Version: KDU
          Audio Driver Version: FMOD version 3.750000
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Not Connected
          Settings mode: Firestorm
          Viewer Skin: firestorm (grey)
          Font Used: Deja Vu (96)
          Draw distance: 128
          Bandwidth: 500
          LOD factor: 10
          Built with MSVC version 1600
          Packets Lost: 1/4,397 (0.0%)

          Show
          hikaruashida Lerochelle Destiny added a comment - I keep getting this, or just crashing to desktop. As a result, I cannot build anything. Seems to happen most when building or manipulating prims. **** Firestorm 4.2.2 (29837) Aug 27 2012 19:20:05 (Firestorm-Release) Release Notes You are at 214,305.0, 252,606.0, 1,117.2 in Imagine Isla located at sim3241.agni.lindenlab.com (216.82.1.95:12035) Second Life RC Magnum 12.11.09.266804 Release Notes CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (3093.02 MHz) Memory: 8174 MB OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce GTX 550 Ti/PCIe/SSE2 Windows Graphics Driver Version: 9.18.0013.0697 OpenGL Version: 4.2.0 RestrainedLove API: (disabled) libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1 J2C Decoder Version: KDU Audio Driver Version: FMOD version 3.750000 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Not Connected Settings mode: Firestorm Viewer Skin: firestorm (grey) Font Used: Deja Vu (96) Draw distance: 128 Bandwidth: 500 LOD factor: 10 Built with MSVC version 1600 Packets Lost: 1/4,397 (0.0%)
          Hide
          whirly.fizzle Whirly Fizzle added a comment - - edited

          Hiya lerochelle,

          Your LOD is set awefully high. From your system information: LOD factor: 10

          This can make you pretty unstable.
          Please lower your LOD setting to an absolute maximum of 4. You can change this setting from quick preferences.
          Let us know if this improves matters for you.

          Show
          whirly.fizzle Whirly Fizzle added a comment - - edited Hiya lerochelle, Your LOD is set awefully high. From your system information: LOD factor: 10 This can make you pretty unstable. Please lower your LOD setting to an absolute maximum of 4. You can change this setting from quick preferences. Let us know if this improves matters for you.
          Hide
          davido_chrome Davido Chrome added a comment -

          All objects that are well done should appear indistinguishable at LOD 3 and 4. If done right, the detail that is lost is too small to see anyway at the distance where it kicks in. And other details can be incorporated in the textures at lower LODs without it being noticeable. If you have your LOD at 10, your viewer will try to render EVERYTHING you see at full detail. That should lead to out of memory crashes and just plain out of graphics processing power, it would be strange otherwise.

          All game uses an LOD system like this, our computers aren't fast enough by far to handle the detail levels you see in todays games if everything on screen is always rendered at highest detail. So the games switches to simpler models when at a distance that doesn't have the details that get lost between pixels anyway.

          Wait five years and things may change though, once we have computers that can handle that level of rendering in real time I bet game creators will stop going through the hazzle of doing several LOD models for each object...

          Show
          davido_chrome Davido Chrome added a comment - All objects that are well done should appear indistinguishable at LOD 3 and 4. If done right, the detail that is lost is too small to see anyway at the distance where it kicks in. And other details can be incorporated in the textures at lower LODs without it being noticeable. If you have your LOD at 10, your viewer will try to render EVERYTHING you see at full detail. That should lead to out of memory crashes and just plain out of graphics processing power, it would be strange otherwise. All game uses an LOD system like this, our computers aren't fast enough by far to handle the detail levels you see in todays games if everything on screen is always rendered at highest detail. So the games switches to simpler models when at a distance that doesn't have the details that get lost between pixels anyway. Wait five years and things may change though, once we have computers that can handle that level of rendering in real time I bet game creators will stop going through the hazzle of doing several LOD models for each object...
          Hide
          trugianni Mona Taylor added a comment -

          hi having the same issue
          CPU: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz (2494.36 MHz)
          Memory: 6092 MB
          OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
          Graphics Card Vendor: Intel
          Graphics Card: Intel(R) HD Graphics Family

          Windows Graphics Driver Version: 8.15.0010.2455
          OpenGL Version: 3.1.0 - Build 8.15.10.2455

          RestrainedLove API: RLV v2.7.0 / RLVa v1.4.7a
          libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
          J2C Decoder Version: KDU
          Audio Driver Version: FMOD version 3.750000
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Vivox 2.1.3010.6270

          Show
          trugianni Mona Taylor added a comment - hi having the same issue CPU: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz (2494.36 MHz) Memory: 6092 MB OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601) Graphics Card Vendor: Intel Graphics Card: Intel(R) HD Graphics Family Windows Graphics Driver Version: 8.15.0010.2455 OpenGL Version: 3.1.0 - Build 8.15.10.2455 RestrainedLove API: RLV v2.7.0 / RLVa v1.4.7a libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1 J2C Decoder Version: KDU Audio Driver Version: FMOD version 3.750000 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Vivox 2.1.3010.6270
          Hide
          spyder haifisch David Batchelor added a comment -

          Same message except .cpp(1738)
          Firestorm 4.4.2 (34167) Jul 1 2013 23:33:25 (Firestorm-Release) with Havok support
          Release Notes

          CPU: Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz (2666.65 MHz)
          Memory: 8191 MB
          OS Version: Microsoft Windows 8 64-bit (Build 9200) compatibility mode. Real version: 6.3 (Build 9600)
          Graphics Card Vendor: NVIDIA Corporation
          Graphics Card: GeForce GTX 460/PCIe/SSE2

          Windows Graphics Driver Version: 9.18.0013.3158
          OpenGL Version: 4.4.0

          RestrainedLove API: (disabled)
          libcurl Version: libcurl/7.21.1 OpenSSL/1.0.0d zlib/1.2.5 c-ares/1.7.1
          J2C Decoder Version: KDU v7.1
          Audio Driver Version: FMOD version 3.750000
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Vivox 2.1.3010.6270

          Settings mode: Firestorm
          Viewer Skin: Firestorm (Grey)
          Font Used: Deja Vu (96)
          Draw distance: 1024
          Bandwidth: 500
          LOD factor: 4
          Render quality: High (5/7)
          Built with MSVC version 1600
          Packets Lost: 0/76,363 (0.0%)

          Show
          spyder haifisch David Batchelor added a comment - Same message except .cpp(1738) Firestorm 4.4.2 (34167) Jul 1 2013 23:33:25 (Firestorm-Release) with Havok support Release Notes CPU: Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz (2666.65 MHz) Memory: 8191 MB OS Version: Microsoft Windows 8 64-bit (Build 9200) compatibility mode. Real version: 6.3 (Build 9600) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce GTX 460/PCIe/SSE2 Windows Graphics Driver Version: 9.18.0013.3158 OpenGL Version: 4.4.0 RestrainedLove API: (disabled) libcurl Version: libcurl/7.21.1 OpenSSL/1.0.0d zlib/1.2.5 c-ares/1.7.1 J2C Decoder Version: KDU v7.1 Audio Driver Version: FMOD version 3.750000 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Vivox 2.1.3010.6270 Settings mode: Firestorm Viewer Skin: Firestorm (Grey) Font Used: Deja Vu (96) Draw distance: 1024 Bandwidth: 500 LOD factor: 4 Render quality: High (5/7) Built with MSVC version 1600 Packets Lost: 0/76,363 (0.0%)
          Hide
          jo yardley Jo Yardley added a comment -

          I see this is an old still open bug but it is happening to me with the firestorm beta 4.7.1.45325 on a brand new Macbook pro.

          Show
          jo yardley Jo Yardley added a comment - I see this is an old still open bug but it is happening to me with the firestorm beta 4.7.1.45325 on a brand new Macbook pro.
          Hide
          JeremiahWhitfield Jeremiah Whitfield added a comment -

          I was having this issue a lot, so I decided to ditch my AMD HD7750 for a NVIDIA GTX450 and guess what , this issue is still affecting me in crowded places (

          Show
          JeremiahWhitfield Jeremiah Whitfield added a comment - I was having this issue a lot, so I decided to ditch my AMD HD7750 for a NVIDIA GTX450 and guess what , this issue is still affecting me in crowded places (
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Jo Yardley
          Are you using the 32bit Mac version? If so, that will still be prone to out of memory crashes. It shouldnt happen at all if you use the 64bit viewer. If you file a JIRA issue giving system information & logs, we can check if it really is an out of memory crash - http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs

          Show
          whirly.fizzle Whirly Fizzle added a comment - Jo Yardley Are you using the 32bit Mac version? If so, that will still be prone to out of memory crashes. It shouldnt happen at all if you use the 64bit viewer. If you file a JIRA issue giving system information & logs, we can check if it really is an out of memory crash - http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Jeremiah Whitfield
          Please file a new JIRA issue giving system information & logs & we can take a look - http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs

          Show
          whirly.fizzle Whirly Fizzle added a comment - Jeremiah Whitfield Please file a new JIRA issue giving system information & logs & we can take a look - http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs
          Hide
          jo yardley Jo Yardley added a comment -

          Ok noob time here, but how do I know which version I'm using?
          I think I got the 64bit version;

          irestorm 4.7.1 (45325) Apr 30 2015 16:03:52 (Firestorm-Beta) with Havok support
          Release Notes

          CPU: Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz (2700 MHz)
          Memory: 8192 MB
          OS Version: Mac OS X 10.10.3 Darwin 14.3.0 Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64 x86_64
          Graphics Card Vendor: Intel
          Graphics Card: Intel(R) Iris(TM) Graphics 6100

          OpenGL Version: 2.1 INTEL-10.6.20

          RestrainedLove API: (disabled)
          libcurl Version: libcurl/7.38.0 OpenSSL/1.0.1i zlib/1.2.8
          J2C Decoder Version: KDU v7.5
          Audio Driver Version: FMOD Ex 4.44.41
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Not Connected
          Settings mode: Firestorm
          Viewer Skin: Firestorm (Grey)
          Font Used: Deja Vu (96)
          Draw distance: 3410
          Bandwidth: 1450
          LOD factor: 4
          Render quality: Ultra (7/7)
          Advanced Lighting Model: Yes
          Texture memory: 512 MB (1)
          VFS (cache) creation time (UTC): 2015-6-22T3:13:7
          Built with GCC version 40201

          Show
          jo yardley Jo Yardley added a comment - Ok noob time here, but how do I know which version I'm using? I think I got the 64bit version; irestorm 4.7.1 (45325) Apr 30 2015 16:03:52 (Firestorm-Beta) with Havok support Release Notes CPU: Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz (2700 MHz) Memory: 8192 MB OS Version: Mac OS X 10.10.3 Darwin 14.3.0 Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64 x86_64 Graphics Card Vendor: Intel Graphics Card: Intel(R) Iris(TM) Graphics 6100 OpenGL Version: 2.1 INTEL-10.6.20 RestrainedLove API: (disabled) libcurl Version: libcurl/7.38.0 OpenSSL/1.0.1i zlib/1.2.8 J2C Decoder Version: KDU v7.5 Audio Driver Version: FMOD Ex 4.44.41 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Not Connected Settings mode: Firestorm Viewer Skin: Firestorm (Grey) Font Used: Deja Vu (96) Draw distance: 3410 Bandwidth: 1450 LOD factor: 4 Render quality: Ultra (7/7) Advanced Lighting Model: Yes Texture memory: 512 MB (1) VFS (cache) creation time (UTC): 2015-6-22T3:13:7 Built with GCC version 40201
          Hide
          jo yardley Jo Yardley added a comment -

          My logs

          Show
          jo yardley Jo Yardley added a comment - My logs
          Hide
          jo yardley Jo Yardley added a comment -

          Ok, forget my posts, sorry about being such a noob, but I guess I had not downloaded the 64 version...
          I've done so now and have been running firestorm set to ultra with shadows and taking pcitures without any issues.
          So I guess that's what I was doing wrong...
          Sorry.

          /me blushes

          Show
          jo yardley Jo Yardley added a comment - Ok, forget my posts, sorry about being such a noob, but I guess I had not downloaded the 64 version... I've done so now and have been running firestorm set to ultra with shadows and taking pcitures without any issues. So I guess that's what I was doing wrong... Sorry. /me blushes
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Jo Yardley
          Great! Glad thats all the problem was & thanks for letting us know.
          The system info you gave was from the 32bit Mac version yes.
          I'm pretty sure you will be fine now you changed over to the 64bit build. Keeping fingers crossed!

          Show
          whirly.fizzle Whirly Fizzle added a comment - Jo Yardley Great! Glad thats all the problem was & thanks for letting us know. The system info you gave was from the 32bit Mac version yes. I'm pretty sure you will be fine now you changed over to the 64bit build. Keeping fingers crossed!
          Hide
          SairaNSunfire96 Saira Nitya Sunfire (AliceP27V% Resident) added a comment - - edited

          Heyas! sooo, I've been getting this error message/glitch since December 2015 on the newer versions, so i downgraded for a bit, a couple weeks ago, i figured I'd try upgrading to the latest version again, and now I'm getting it on every version, no matter what.

          For me though, it goes like this: I'll log in, and the cache will load as if i cleared it (even when i never did), then it'll freeze, go unresponsive, & crash upon the cache finishing loading. i only figured out it was this glitch when the popup came up once telling me so. anyways, here's my crash logs & such, in the attached files, and a screenshot of the popup i got, really hoping you all can help me find a solution, cause firestorm is completely unusable for me till i get this fixed.

          edit: sorry, probably should've done something to differentiate mine from the others, didn't think of it, i can re-upload if you need me to.

          Show
          SairaNSunfire96 Saira Nitya Sunfire (AliceP27V% Resident) added a comment - - edited Heyas! sooo, I've been getting this error message/glitch since December 2015 on the newer versions, so i downgraded for a bit, a couple weeks ago, i figured I'd try upgrading to the latest version again, and now I'm getting it on every version, no matter what. For me though, it goes like this: I'll log in, and the cache will load as if i cleared it (even when i never did), then it'll freeze, go unresponsive, & crash upon the cache finishing loading. i only figured out it was this glitch when the popup came up once telling me so. anyways, here's my crash logs & such, in the attached files, and a screenshot of the popup i got, really hoping you all can help me find a solution, cause firestorm is completely unusable for me till i get this fixed. edit: sorry, probably should've done something to differentiate mine from the others, didn't think of it, i can re-upload if you need me to.
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Saira Nitya Sunfire (AliceP27V% Resident)
          Thanks for the logs.

          Firestorm-Releasex64 4.7.5.47975
          OS info: Microsoft Windows 10 64-bit (Build 10240)
          Intel(R) HD Graphics 4400
          4.2.0 - Build 10.18.10.4252

          Hmm hard to say what happened that session. The log just cuts dead & I don't know if that's because you were still logged in when you copied the log or whether the viewer froze.
          From your description it sounds like it may be an inventory problem however.
          Are you able to login alt accounts & keep those logged in and stable?
          Can you also test for me if you can stay logged in with the affected account on the LL viewer: https://secondlife.com/support/downloads/

          The next time this crash/freeze happens, before relaunching the viewer, zip up the whole logs folder & attach it to this issue using More Actions -> Attach files.
          This page tells you where to find the logs folder: http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs

          Can you also go to Help -> About Firestorm, click the "Copy to clipboard" button & paste all your system information into a comment here.
          Thanks!

          Show
          whirly.fizzle Whirly Fizzle added a comment - Saira Nitya Sunfire (AliceP27V% Resident) Thanks for the logs. Firestorm-Releasex64 4.7.5.47975 OS info: Microsoft Windows 10 64-bit (Build 10240) Intel(R) HD Graphics 4400 4.2.0 - Build 10.18.10.4252 Hmm hard to say what happened that session. The log just cuts dead & I don't know if that's because you were still logged in when you copied the log or whether the viewer froze. From your description it sounds like it may be an inventory problem however. Are you able to login alt accounts & keep those logged in and stable? Can you also test for me if you can stay logged in with the affected account on the LL viewer: https://secondlife.com/support/downloads/ The next time this crash/freeze happens, before relaunching the viewer, zip up the whole logs folder & attach it to this issue using More Actions -> Attach files. This page tells you where to find the logs folder: http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs Can you also go to Help -> About Firestorm, click the "Copy to clipboard" button & paste all your system information into a comment here. Thanks!
          Hide
          SairaNSunfire96 Saira Nitya Sunfire (AliceP27V% Resident) added a comment -

          Heyas! so, someone in the firestorm support channel did suggest the alt account thing before, it did turn out it's only my main account, sorry i forgot to mention it, been a tad frustrated, plus i got college classes. also; when the viewer freezes, it does that "program has gone unresponsive" popup like i mentioned (though i probably could've explained it better, sorry), so that might be why the log just stops. anyways, I'll try the default viewer in a sec, but i figured I'd post that info & the system info you asked for first, so here's that:

          Firestorm 4.7.5 (47975) Nov 9 2015 18:48:20 (Firestorm-Releasex64) with OpenSimulator support
          Release Notes

          CPU: Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz (3691.48 MHz)
          Memory: 8109 MB
          OS Version: Microsoft Windows 10 64-bit (Build 10240)
          Graphics Card Vendor: Intel
          Graphics Card: Intel(R) HD Graphics 4400

          Windows Graphics Driver Version: 10.18.0010.4252
          OpenGL Version: 4.2.0 - Build 10.18.10.4252

          RestrainedLove API: (disabled)
          libcurl Version: libcurl/7.38.0 OpenSSL/1.0.1i zlib/1.2.8
          J2C Decoder Version: KDU v7.7
          Audio Driver Version: FMOD Ex 4.44.56
          Qt Webkit Version: 4.7.1 (version number hard-coded)
          Voice Server Version: Not Connected
          Settings mode: Firestorm
          Viewer Skin: Firestorm (Grey)
          Font Used: Deja Vu (96 dpi)
          Font Size Adjustment: 0 pt
          UI Scaling: 1
          Draw distance: 128 m
          Bandwidth: 1500 kbit/s
          LOD factor: 2
          Render quality: Medium (3/7)
          Advanced Lighting Model: No
          Texture memory: 1024 MB (1)
          VFS (cache) creation time (UTC): unknown
          Built with MSVC version 1800

          Show
          SairaNSunfire96 Saira Nitya Sunfire (AliceP27V% Resident) added a comment - Heyas! so, someone in the firestorm support channel did suggest the alt account thing before, it did turn out it's only my main account, sorry i forgot to mention it, been a tad frustrated, plus i got college classes. also; when the viewer freezes, it does that "program has gone unresponsive" popup like i mentioned (though i probably could've explained it better, sorry), so that might be why the log just stops. anyways, I'll try the default viewer in a sec, but i figured I'd post that info & the system info you asked for first, so here's that: Firestorm 4.7.5 (47975) Nov 9 2015 18:48:20 (Firestorm-Releasex64) with OpenSimulator support Release Notes CPU: Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz (3691.48 MHz) Memory: 8109 MB OS Version: Microsoft Windows 10 64-bit (Build 10240) Graphics Card Vendor: Intel Graphics Card: Intel(R) HD Graphics 4400 Windows Graphics Driver Version: 10.18.0010.4252 OpenGL Version: 4.2.0 - Build 10.18.10.4252 RestrainedLove API: (disabled) libcurl Version: libcurl/7.38.0 OpenSSL/1.0.1i zlib/1.2.8 J2C Decoder Version: KDU v7.7 Audio Driver Version: FMOD Ex 4.44.56 Qt Webkit Version: 4.7.1 (version number hard-coded) Voice Server Version: Not Connected Settings mode: Firestorm Viewer Skin: Firestorm (Grey) Font Used: Deja Vu (96 dpi) Font Size Adjustment: 0 pt UI Scaling: 1 Draw distance: 128 m Bandwidth: 1500 kbit/s LOD factor: 2 Render quality: Medium (3/7) Advanced Lighting Model: No Texture memory: 1024 MB (1) VFS (cache) creation time (UTC): unknown Built with MSVC version 1800
          Hide
          SairaNSunfire96 Saira Nitya Sunfire (AliceP27V% Resident) added a comment -

          K, sooo, just tried it with the SL Default viewer, got the same crash. here's the crashlogs, via attachment:

          Show
          SairaNSunfire96 Saira Nitya Sunfire (AliceP27V% Resident) added a comment - K, sooo, just tried it with the SL Default viewer, got the same crash. here's the crashlogs, via attachment:
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Saira Nitya Sunfire (AliceP27V% Resident)
          Thanks!

          Okay so it's looking pretty certain it's an inventory issue on the affected account.

          From your LL viewer log:
          Second Life Release 4.0.1.310054

          Login button clicked at T23:48:47
          Login request sent by viewer at: T23:48:57
          Login request received back at: T23:50:09 (that's really quite slow... this is where you will see "Logging in..." on the login screen)
          Creating inventory views starts at: T23:50:18
          Creating inventory views ends at: T23:50:23 (5 seconds to create inventory views - this is fine).
          Login completes at: T23:50:24
          Total login time: 1 min 37 seconds.

          Total login time is pretty slow & it's risking a time out but you do get fully logged in.
          Most of that time (1 min 12 seconds) is waiting for the reply from the login server.

          You have problems connecting to voice in both FS & LL viewer logs too, though doubtful if this is related to your problem.

          Log cuts dead at T00:23:34, so you manage to stay inworld ~30 mins before the viewer freezes.
          If the problem was something going wrong with the inventory, I would have expected you to either time out during login or for the viewer to freeze quicker then this after login.
          Roughly how large is your inventory?

          You hinted above that your inventory is always empty when you login s if you had cleared cache, but you didn't, and that the viewer freezes once inventory is about fully fetched. can you just clarify that? Does the freeze always seem to happen just as inventory is fully fetched?

          Because this does look like it's some kind of account specific inventory issue, best thing to do is to file a support ticket with Linden lab support at https://support.secondlife.com/create-case/ and ask for your inventory to be checked for problems.
          You will get a Scout at first & they will make you do all the usual things (cache clear etc etc) so make it clear to them that this problem happens on both the LL viewer and Firestorm and it only affects one of your accounts, that you suspect it's an inventory problem and they should escalate your ticket to an actual support Linden that will check your inventory.

          This usually takes a few days to get a ticket escalated so what you can do in the mean time is, try to login on Radegast text viewer: http://radegast.org/wiki/Radegast_Download
          It's quite likely that this viewer will not freeze, though it depends where the problem is.
          Examine your inventory on Radegast & see if you can spot anything amiss - for example folders outside or root inventory or multiple system folders or an excessive number of calling cards.

          Show
          whirly.fizzle Whirly Fizzle added a comment - Saira Nitya Sunfire (AliceP27V% Resident) Thanks! Okay so it's looking pretty certain it's an inventory issue on the affected account. From your LL viewer log: Second Life Release 4.0.1.310054 Login button clicked at T23:48:47 Login request sent by viewer at: T23:48:57 Login request received back at: T23:50:09 (that's really quite slow... this is where you will see "Logging in..." on the login screen) Creating inventory views starts at: T23:50:18 Creating inventory views ends at: T23:50:23 (5 seconds to create inventory views - this is fine). Login completes at: T23:50:24 Total login time: 1 min 37 seconds. Total login time is pretty slow & it's risking a time out but you do get fully logged in. Most of that time (1 min 12 seconds) is waiting for the reply from the login server. You have problems connecting to voice in both FS & LL viewer logs too, though doubtful if this is related to your problem. Log cuts dead at T00:23:34, so you manage to stay inworld ~30 mins before the viewer freezes. If the problem was something going wrong with the inventory, I would have expected you to either time out during login or for the viewer to freeze quicker then this after login. Roughly how large is your inventory? You hinted above that your inventory is always empty when you login s if you had cleared cache, but you didn't, and that the viewer freezes once inventory is about fully fetched. can you just clarify that? Does the freeze always seem to happen just as inventory is fully fetched? Because this does look like it's some kind of account specific inventory issue, best thing to do is to file a support ticket with Linden lab support at https://support.secondlife.com/create-case/ and ask for your inventory to be checked for problems. You will get a Scout at first & they will make you do all the usual things (cache clear etc etc) so make it clear to them that this problem happens on both the LL viewer and Firestorm and it only affects one of your accounts, that you suspect it's an inventory problem and they should escalate your ticket to an actual support Linden that will check your inventory. This usually takes a few days to get a ticket escalated so what you can do in the mean time is, try to login on Radegast text viewer: http://radegast.org/wiki/Radegast_Download It's quite likely that this viewer will not freeze, though it depends where the problem is. Examine your inventory on Radegast & see if you can spot anything amiss - for example folders outside or root inventory or multiple system folders or an excessive number of calling cards.
          Hide
          SairaNSunfire96 Saira Nitya Sunfire (AliceP27V% Resident) added a comment -

          well, my inventory is about 160k items or so, though it's mainly ocd'd organization via copies that i was gonna fix, then this happened & i realized how much stuff 160k items really is when i tried to reorganize it as a first try, while crashing every login. >_<'

          also; it's not really that the inventory is empty, all the folders on the top level show up, but at the bottom it shows that "fetching "# here" items..." which tends to freeze at around 160k items, though every now & then it freezes at around 145k items. and yeah, the freeze always seems to happen as soon as it gets to 160k items, with the exception of the rare 145k, which has happened at most twice i think.

          oh! also; just remembered (sorry, my memory can make an alzheimer's patient's look good sometimes ><'), the main reason i stopped just trying to clean my inventory was actually cause i found something that said it's possible for the calling cards glitch to happen with Landmarks, and for whatever reason, i'd never heard of that before, and it turns out, every content creator just HAS to have their LMs to their mainstores in their boxes, so i didn't realize until then all my copies also had copies of the LMs, meaning i had enough LMs it'd take possibly months+ to clean em all out. ><'

          i'll try the Second Life thing & see if they can help, thanks for all the help so far.

          Show
          SairaNSunfire96 Saira Nitya Sunfire (AliceP27V% Resident) added a comment - well, my inventory is about 160k items or so, though it's mainly ocd'd organization via copies that i was gonna fix, then this happened & i realized how much stuff 160k items really is when i tried to reorganize it as a first try, while crashing every login. >_<' also; it's not really that the inventory is empty, all the folders on the top level show up, but at the bottom it shows that "fetching "# here" items..." which tends to freeze at around 160k items, though every now & then it freezes at around 145k items. and yeah, the freeze always seems to happen as soon as it gets to 160k items, with the exception of the rare 145k, which has happened at most twice i think. oh! also; just remembered (sorry, my memory can make an alzheimer's patient's look good sometimes > <'), the main reason i stopped just trying to clean my inventory was actually cause i found something that said it's possible for the calling cards glitch to happen with Landmarks, and for whatever reason, i'd never heard of that before, and it turns out, every content creator just HAS to have their LMs to their mainstores in their boxes, so i didn't realize until then all my copies also had copies of the LMs, meaning i had enough LMs it'd take possibly months+ to clean em all out. > <' i'll try the Second Life thing & see if they can help, thanks for all the help so far.
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Welcome
          Comment back here if you have any problems getting your inventory checked or when support get you fixed.

          Show
          whirly.fizzle Whirly Fizzle added a comment - Welcome Comment back here if you have any problems getting your inventory checked or when support get you fixed.

            People

            • Assignee:
              nickyd Nicky
              Reporter:
              adama thetan Adama Thetan
            • Votes:
              26 Vote for this issue
              Watchers:
              24 Start watching this issue

              Dates

              • Created:
                Updated: