|
|
|
Similar situation to Ron's here, crash seems to occure when 2 of the 3 GB are used up.
Similaritys: intel dual core cpu with 3GB under XPSP2. I have had the same error show up in the last two releases of WindLight. It seems to happen quicker in busy settings, busy clubs, lots of people, lots of flashing lights, etc. Just went to bad girls and it happened about 15 min in, or so. Wasn't watching My memory, so I can't comment on that, but I've 2mb, Athlon 3800+, XP patched this week...
Hope this helps.... Pirate UPDATE 12/28 - I'm no longer using WindLight until this is fixed. It's pretty, I'm sure all the gamma issues made it even prettier, but I'll never know UPDATE 1/11 Second Life 1.18.6 (76886) Jan 3 2008 17:26:44 (Second Life WindLight) exhibits the same behavior. UPDATE 1/23 Second Life 1.18.6 (77495) Jan 22 2008 15:30:40 (Second Life WindLight) I notice that when I spend enough time in GOL 4 at Sensual Elements, memory usage slowly but steadily increases until about 61%-62% of my available physical RAM (3GB) is in use. By then I can almost certainly expect the smart heap error message, but more often than not I'm able to ignore it, start detaching non-essential HUD objects, close IM and chat window, my inventory and the chat bar, and prepare to log off.
However, SL brings the error message up again at the precise moment of logout, then crashes when answering it with 'Ignore' again. This prompts the viewer to ask whether to send a crash report on the next startup. (I've clicked yes but don't know if any report actually gets sent as it seems to go so quickly...) Note that whenever the error window pops up, SL gets put "on hold" but resumes normally once I click Ignore (at least the first few times)...so it's not really a crash at that point. I have the same problem. It's the first Windlight that causes crashes for me.
Second Life 1.18.6 (76116) Dec 19 2007 09:54:25 (Second Life WindLight) CPU: Intel Core 2 Series Processor (2131 MHz) It's not just Windlight - I've been using RC 1.18.6.2 today because of problems with my Nicholaz BE-v, and had it two or three times already.
Dell Inspiron 8600 Yeah, so I bump into things a lot - I'm normally fine for hours, even if I'm slow. Happening for me too, when showing object owned by others on my property.
Second Life 1.18.6 (76453) CPU: Intel Core 2 Series Processor (2393 MHz) I've seen this too – since it's not just WindLight, I'm changing Affects Version/s on this. This has happened to me too; sometimes I've noticed it after taking a series of snapshots, but I'm not sure if that's the cause.
Importing it for further investigation, and thanks a lot for reporting it and commenting! Happens for me as well if I run SL WindLight long enough. Usually after 2 hours, SecondLifeWindLight.exe *32 is using more than a gig of RAM. Tried lowering video memory, didn't help. Also tried disabling Object-Object Occlusion with no luck. Might have something to do with all the memory leaks in SL. I can stay in one sim with hardly no traffic whiling staring at the ground, and yet watch my memory usage slowly increase in KB increments... along with Handles, which will increase over 3000 (wow, usually I see games max at 1K). Though, GDI Object usage has gotten a lot better (doesn't hardly ever go over 100 anymore). Must suck to be a SL Developer... g'luck guys in fixing these issues..
EDIT Also Page Faults were over 20 Million when it crashed. Not suprised as IO intensive SL is, but still, that's a lot of exceptions in a course of a few hours. Microsoft Vista Ultimate 64 bit (Build 6000) Happening to me too. No snapshots - but was in a veryyyyy crowded laggy sim when it started. My entire computer had trouble shutting down after this.
Windows XP (SP2) I attached a screenshot of my crash. Notice the Page Faults and the Memory Usage. I hit retry on both dialogs and was able to continue using SL for only a few minutes until it crashed again.
EDIT My SecondLife WindLight Version: 1.18.6 (76886) CPU: Intel Pentium 4 (Unknown model) (3214 MHz)
Memory: 2048 MB OS Version: Microsoft Windows XP Service Pack 3, v.3244 (Build 2600) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 7300 GT/PCI/SSE2 OpenGL Version: 2.1.1 LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000) Packets Lost: 2/31273 (0.0%) Viewer Digest: 58f7490d-4744-f65f-8845-3f6b997152e6 this happend when I tp'd into about 15 people in a close area. From Steve Linden, who's been looking at various bugs of this kind:
"This is a dupe of other memory leak bugs. SmartHeap Library "out of memory" errors. After spending merely several hours just sitting at an infohub and chatting.
At time of first error, SecondLifeWindlight.exe using approximately 1.3G, then started spamming the "SmartHeap" dialog (hit ignore repeatedly) and eventually crashed. After restarting client, is only using approximately 390k. You are at 262685.9, 252791.5, 112.8 in Bear located at sim4361.agni.lindenlab.com (63.210.158.11:12035) CPU: Intel Core 2 Series Processor (3000 MHz) Same error. Windlight 1.19.0 (79185) was only using 700K out of 2G total RAM! This doesn't look like a memory leak, I'd just logged in and it was hardly using any RAM at all by SL standards!
CPU: AMD (Unknown model) (2499 MHz) This has happened to me twice in the last couple days. Both times has been after being idle for long periods of time – come back to PC to find this error. This coincided with a video card upgrade and adding RAM to machine.
Second Life 1.19.0 (80044) Feb 15 2008 16:46:46 (Second Life WindLight) CPU: Intel Core 2 Series Processor (1862 MHz) I have all the similar computer upgrades to accomodate SL as well as clear cache and dump cookies all the time. My hard drive is 80% empty. It happened twice last night. It is always in the evenings and more often than not--crowded sims. I am not savy enuf to try some of the program alterations that I see around the internet so hope you guys can fix this nasty problem! BTW, I use Windlight and have had this crash probably 20 times by now.
I am seeing this now in the RELEASED version of the client.
 This seriously needs to be FIXED! Had this twice today, never seen it before I updated to: Second Life 1.19.0 (5) Feb 28 2008 17:18:12 (Second Life Release)
Both times it happened on a virtually empty SIM and I had been logged on for a couple of hours. Clicking Retry the error box immediately comes back and clicking Ignore SL instantly crashes. Yeh I keep having so many problems lately with Windlight. First thing its reading my cpu wrong. I have the Intel e8400 and 4GB of DDR2 800 ram. This "Out of Memory" is quite annoying and happens at the wrong times.
CPU: Intel Pentium III/Pentium III Xeon (0.25 micron process) with external L2 cache (2999 MHz) Rico: what it's reporting is probably correct. Half a gig is pretty typical memory waste for a 32-bit OS on a modern motherboard, and the current crop of Intel processors are all based on the Pentium III core (the Pentium 4 was basically one big nasty dead end).
lol. Yeah I just figured it would say – Intel Core 2 Series Processor – like everybody else. shrugs My setup was running great before the latest patches that came out. crosses fingers for a better patch release
I have this problem many times a day since I updated to viewer 1.19.0. My issue reproduces itself when I'm in a script heavy, high detail and/or roleplay environment. I don't have to be doing anything more than looking around. I also get this error when I'm using my camera movements in laggy areas. I'm NOT using windlight, My OS is Win Vista PRO 64bit.
Second Life Server 1.19.1.81132 CPU: Intel Core 2 Series Processor (3059 MHz) Given the nature of this bug, I say it'll be a while until it gets fixed. If the memory leak isn't occurring in the second life developer's code, then it's probably from one of its dependencies. This means they'll either have to wait for it to be fixed by the creators of the dependency or resort to a different solution that might introduce more problems (which might even take longer to resolve).
I don't agree with them releasing a replicable version. Due to the severity of this bug, it should have been on their top priority list. To me, this isn't fulfilling their promise in making second life more optimal and stable, but at least now they have a reason to. Anyway, vista and 3rd party venders with its incompatibility and lack of support for older hardware and DirectX 9/OpenGL games causes the majority of my second life problems. If only Vista's upgrade hadn't voided my XP upgrade license... I don't think it's an actual memory leak. If it was a memory leak it wouldn't be popping up claiming it couldn't allocate memory when I still had 1.3GB of RAM left. It's corruption in Smartheap itself, and there's been discussion (mentioned here and on the SLdev mailing list) about switching from Smartheap because of issues like this.
No doubt that's a problem in itself, but just because an error message pops up saying you're out of memory when you obviously have more doesn't necessarily mean it's not caused by a memory leak. Most of us are reporting how quickly this error occurs and if you watch carefully, you'll notice that second life never releases any of its resources. It just keeps growing, sometimes more rapid than others. Granted I'm not a second life developer so either way it's hard for me to say. I was just basing what I said on what Torley Linden said when he quoted Steve Linden that this bug was a duplicate of other memory leak bugs, so I wouldn't rule it out just yet.
One last thought, the SmartHeap Library is used to improve memory management performance for multi-threaded, memory intensive, software in multi-core systems. It also provides memory/heap leak detection (though I personally would still use VLD or CRTDBG). And SmartHeap 8.1 does support both XP/Vista 32/64 bit. The developers, I'm sure, already know all this, but if they do decide to replace it, I hope it's something equivalent or better. Keep your fingers crossed!
Whether there's a memory leak or not, if Smartheap is bringing up a dialog claiming there's no memory available when there's plenty of memory available, then either there's a bug in Smartheap or something's corrupted the data structures it's using... that is, a memory leak is not the root cause of this particular bug.
Or something is conflicting with SmartHeap Library (which is the likely scenario). My guess is they either have an older version or they added something that's causing the conflict...
Again, SmartHeap Library handles the memory management of the program (it replaces the ANSI memory allocation methods with its own). Memory is consumed to the point that about 75% of total memory resources are being used. In which results in an "Out of memory" dialog generated by SmartHeap Library handling the exception. In all cases, we all claim to have more memory, right? But notice that some of us generate this error when memory consumption is above "SL standards". For some of us it's occurring when SL consumes about 1GB to over 2GBs of memory, and all this memory is consumed in less than a few minutes to a few hours without a single bit of memory being freed. How is this not a memory leak? IMO, Second Life should never even reach over the recommend 1GB of memory. Still, I'm not saying that fixing this conflict won't fix the problems it's having with memory management. In fact I think this is what Steve Linden was talking about, that the two are related. Who knows... Either way it's pointless to debate since we're not developers of second life, just be patient for them to work it out... "Or something is conflicting with SmartHeap Library" – that's "or something's corrupted the data structures it's using".
"Memory is consumed to the point that about 75% of total memory resources are being used. In which results in an "Out of memory" dialog generated by SmartHeap Library handling the exception." - around 700M out of 2GB isn't "75% of total memory resources". And SL doesn't go much over 700M for me, even after hours of use. "How is this not a memory leak?" - It's only a memory leak if SL is not actually using that memory (for example, for textures and objects), and doesn't know (directly or though Smartheap) that it's not using it. Even if SL never releases it to the OS that STILL doesn't mean it's a memory leak: memory in the Smartheap pool quite likely won't be returned to the OS. A memory leak is when you have memory that is no longer being used by SL, and that has not been marked as free by SL for Smartheap to reallocate it. A memory leak is a specific kind of memory problem... it's not a general term for any memory applocation problem... and this doesn't have the symptoms of a memory leak, it has the symptoms of heap corruption. There are quite likely memory leaks in SL as well, but this problem does not seem to be symptomatic of memory leaks. "Either way it's pointless to debate since we're not developers of second life" - Sure we are, some of us. We have the source code. We submit patches. What more does it take? Okay, first off, you can't corrupt a data structure, it's impossible, you can however corrupt the memory it's using, then you're talking about memory corruption, not "data structure corruption"... almost all instances of this exact problem in other programs is due to the same two facts, either you really are out of memory or a dependency is "conflicting" with SmartHeap Library's resources.
You said that second life's windlight was using 700 MBs out of 2GBs when this error occurred for you. Just because second life is using 700 MBs doesn't mean you have 1.3 GBs of memory available. I'm pretty sure your operating system and other programs are using a large chunk of that as well. Hence about 75% of "total memory resources", which was a rough estimate based on my tests. You don't have to quote me on that because I'm not stating it as a fact. Look, I'm not saying it is a memory leak. I'm just still not convinced it's not. And everything you stated is based on an assumption, yet you claim it as if it's fact. I know what a memory leak is, and from my findings this bug produces unintentional memory consumption by second life. This is the very definition of a memory leak. In fact, if it wasn't a memory leak then those of us with lots of memory to spare should never receive this dialog. Okay, so it's a heap corruption (memory corruption, same thing). But what if it's corrupting the heap to the point that SmartHeap Library is unable to free or reallocate its memory? Then isn't this a heap corruption that produces a memory leak? And even if it was a heap corruption, which is a bold assumption, second life should crash. It's hard for me to believe that something out there can cause the heap corruption while still allowing a program to function properly. But I don't know, I don't have time to download and debug second life's code. And finally, that doesn't make you a second life developer. That makes you a second life contributor. I trust more what a second life developer says (like Steve Linden) than you, so until a second life developer really comes out and states the actual problem is, it's still up for debate. First: we're saying the same thing using different words. I have no objection to saying "memory corruption". We're in violent agreement there, OK?
Second: the only application running was SL, and that 700 MB was the total memory in use by Windows. So, on my computer, when this came up, there was no evidence of a memory leak. There was evidence of heap corruption. And, yes, it's possible for programs to run for a considerable period with corrupted heaps, and it's possible for them to crash very quickly. That's one of the reasons heap corruption is so hard to debug, and one of the reasons why debugging allocators exist. Finally: there are people out there not working for Linden Labs who are in a position to try and solve this problem for them. Whether you call them developers, contributors, or anything else I don't care: this forum is one of the places where they communicate, and the results of this communication often includes such things as patches to fix problems. Which is, of course, one of the main reasons for having the source and bug tracking system public like this in the first place. Yes, I can agree on that. And also that it is a pain to debug heap/stack corruption, but nevertheless it should be done and it's usually worth the effort.
Which still leaves the question of what exactly is causing the problem? Okay, so taking out SmartHeap Library and replacing it back with CRT functions is a great short term solution, but this is more of a workaround and it pushes second life back a step. Creating a patch that avoids the problem all together yet fixes this particular bug isn't that great of solution either. I would much rather the developers be given the time needed to either replace SmartHeap Library with something that works just as good or better, or fix the actual problem that is occurring. I have much respect for the second life developers, it's not every day you can create solutions that no other game out there does. *EDIT: Second Life 1.19.0 (5) Feb 28 2008 17:18:12 (Second Life Release)
You are at 258330.5, 264398.5, 29.4 in Satellite located at sim3701.agni.lindenlab.com (216.82.22.182:13006) CPU: Intel Pentium 4 (Unknown model) (3198 MHz) Got this issue as well today. It appears to act just like the previous issue I was having where the client would just lock up and go not responding for 5 - 10 seconds at a time for no reason at all, but usually when those would occur the client would eventually recover. But I got this exact error today with the warning pop up and everything, retry did not resolve the issue and ignore caused the client to crash entirely. My OS did not actually have a problem during the error and none of my other applications errored alongside it. I was only actually running one Firefox instance and an instance of Google Chat and had only been logged in for a period of about an hour on the 1.19.0(5) viewer and I was in a low utlization sim simply using the chat interface to field my large stack of IMs. This just happened to me after several gestures failed to load. Could possibly be related?
Found this since my comp started too with thiscrap.....
Quote) "Out-of-memory errors on Windows SmartHeap has no upper limit on how much memory it can manage, so the limit will be that set by the OS. Typically, though, the allocation process wastes some address space, and a process will run out of address space before (sometimes well before) the heap manager has stored 2 GB of data/objects. At that point you get an Out of Memory error. It's important to remember that wasted address space does not equate to wasted physical memory. If you have an extremely large memory pool (more than 128 MB), or if your application is so large (hundreds of megabytes) that address space is short, you should set the SmartHeap page size to 64K. This will minimize wastage of address space. The default SmartHeap page size in Win32 is 16 K. See the SmartHeap Programmer's Guide for additional info. Note that the page size is a per pool value". (Unquote) http://www.bleepingcomputer.com/forums/topic55375.html I´ve been talking tosome ppl in world and they seem to get with multiple windows open..... Some of the cases of out-of-memory may be due to the kind of fragmentation they're talking about, but there's a bigger problem out there as well. What that quote is about is wasted space due to overhead from the memory manager, which causes the application to consume more real memory than it otherwise should for a given set of requests... that would lead to SL growing somewhat faster than expected... but not hugely so. What we're seeing is SmartHeap reporting memory being exhausted when the OS is reporting significant amounts of free memory (in my case, 1.3GB out of 2 GB were still available). Fragmentation wouldn't have that effect.
On the other hand, increasing the SmartHeap page size shouldn't hurt. This problem hits me like clockwork about once every 1.5 hours since 1.19.0, memory usage by SL will slowly climb to about 1.63Gb (out of 2Gb Phys) then smartheap will crash, doesn't matter if I'm in a populated sim or I'm the only one on there. with only one window open.
Second Life 1.19.1 (2) Mar 19 2008 17:40:40 (Second Life Release Candidate) CPU: AMD (Unknown model) (3015 MHz) (Actually a AMD 64 X2 6000) Second Life 1.19.1 (2) Mar 19 2008 17:40:40 (Second Life Release Candidate)
You are at 260652.6, 254185.2, 81.2 in Isabel located at sim5489.agni.lindenlab.com (8.2.34.45:13006) CPU: Intel Core 2 Series Processor (2666 MHz) yes this is an annoying little thing to have happen.. this should eb a show stopper... not critical. Second Life 1.19.0 (5) Feb 28 2008 17:18:12 (Second Life Release)
You are at 259625.2, 232324.9, 97.7 in Hauwai located at sim3874.agni.lindenlab.com (63.210.156.32:13006) CPU: Intel Pentium 4 (Unknown model) (3006 MHz) I too am getting this error, and SL always crashed when I click ignore or anything except retry which does nothing. I had just ported into Minx shop and was rezzing when it happened this time. The Out of memory error occurs also witth the new RC3.
This error can be systematically reproduced using the media video : sUrlPlay = "http://www.google.fr"; //or any other url The media is refreshed all the 10 seconds (by running the same sequence); using the Windows Task Manager, we can observe the Page File size increased regularly until the error. Second Life 1.19.1 (3) Mar 26 2008 12:59:02 (Second Life Release Candidate) You are at 255013.7, 261146.4, 700.5 in Furvata located at sim3684.agni.lindenlab.com (216.82.22.165:13004) CPU: AMD (Unknown model) (2200 MHz) Getting the same issue. I never saw it until the last 2 client releases.
Processor: I'm also getting this issue still. Happened with all the RCs I used and now after updating to the new release, it's still happening.
I can stand around in a sim, completely idle for a few hours then the error will start popping up. I'll be able to hit ignore a few times, but eventually the whole client will crash. I know you've heard it all before, but it's extremely annoying that such a prevalent issue persists. There were plenty of people having this issue with the RCs, but it seems like the issue wasn't even addressed before forcing everyone to upgrade to the newest client. CPU: Intel Core 2 Series Processor (2393 MHz) The first image shows the details in the task manager for Second Life after getting and ignoring my first Smart Heap error but before the program crashed completely.
The second image is after Second Life disconnected me from the sim I was on, I clicked ignore on the next Smart Heap error I got and attempted to log out. The third image is after ignoring the Smart Heap error while logging out and Windows showing that Second Life had crashed. 1.5 GB working set?
I never see more than 500k working set on Windows, or 700k working set on Mac. CPU: AMD (Unknown model) (2390 MHz)
Memory: 2048 MB OS Version: Microsoft Windows XP Service Pack 2 (Build 2600) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 7800 GT/PCI/SSE2/3DNOW! OpenGL Version: 2.0.3 LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.14258 (Mozilla GRE version 1.8.1.13_0000000000) Packets Lost: 26/28503 (0.1%) Viewer Digest: bb2966f6-cf81-a0de-1e21-dcd21f05428a I knew stuff like this would start to happen as soon as we were forced off the old clients. CPU: Intel Core 2 Series Processor (2394 MHz)
Memory: 4094 MB OS Version: Microsoft Windows Vista Service Pack 1 (Build 6001) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 7900 GS/PCI/SSE2 OpenGL Version: 2.1.1 LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.14277 (Mozilla GRE version 1.8.1.13_0000000000) Using the information form the previous posts, I was able to reproduce the symptoms at the Isabel site in AllieKat Stovall's report above. I ran using Rational Purify to detect memory leaks. I saw the memory usage continue to grow quite rapidly, but in my case, when it reached a threshold at about 700Meg, it dropped down suddenly before it started growing again.
Purify detected less than 1Meg of leaks, though. This isn't a memory leak in the sense that programmers mean. When programmaers (and leak detectors) talk about memory leaks, they are referring to memory that can no longer be referenced by the program. In this case, although the memory continues to grow, it is (nearly) all memory that the program knows about. At the Isabel location (30, 229, 81) there is a slide show that generates a new texture every ten seconds or so. I think the memory growth is due to loading these textures. However, when the texture cache reaches a threshold, it is supposed to clear out some of the older textures in order to release memory as it did during my test. So there are a few possible reasons for the problem people are seeing. I'll let you know if I make any more progress. Mike Second Life 1.19.1 (4) Apr 2 2008 11:59:37 (Second Life Release)
You are at 260645.7, 309364.0, 21.4 in The Bay located at sim3750.agni.lindenlab.com (216.82.22.231:13004) CPU: AMD (Unknown model) (2204 MHz) Having the same error here. I have only seen this since the latest 2 viewer updates. I have been getting exactly this issue but ONLY since the Ver 1.19.1.4 release. I was running Windlight as the beta test and RC viewer without this problem.
This is ALSO occuring with the new 1.20 RC viewer, but subjectively with less frequency. intel dual core cpu with 2GB under XPSP2, ATI Radeon 1550 Series Edited to add 1.20.0 RC Viewer
I haven't had this recently, but I've been getting warnings about a bad pointer on exiting.
Windlight 1.18.5.73655 and the viewer 1.18.50(3) was more stable, with windlight 1.18.6.76886 and the viewer up from version 1.19. i had the same problems.
My machine is a Intel 2core 3GHz with 2GB of low latency ram, XPSP2 and Radeon X1650. This just started for me with RC "Out of Memory in Smartheap Library " on Crash could be after an hour or 4 or after 5 min and does not matter where on the grid I am.
Second Life 1.20.2 (85278) Apr 17 2008 19:35:32 (Second Life Release Candidate) CPU: Intel Core 2 Series Processor (1862 MHz) not only that my antialising doesn't work everything is hatchy... even AVatars, the log in screen is blurry as well all the UI once logged in I have ran windight since the beginning NEVER had any crashes like this nor any issues was running 1.20.0 or (1) with ultra custom draw set to 96 and some other minor tweaks. This completely sucks! Second Life 1.20.4 (85828) Apr 24 2008 14:59:50 (Second Life Release Candidate)
CPU: Intel Core 2 Series Processor (2399 MHz) Occurring here too, very frequently. I will often have several gigabytes of RAM left when this occurs, so it seems likely it is related to a virtual memory problem. This seemed better with RC1.20(4) but since 1.20(5) I have been crashing repeatedly after a few minutes either directly to desktop or with a smartheap error. I may have to revert to the normal viewer.... :-/
Still happening to me with both the 1.19.1.4 release viewer and the 1.20 RC6 viewer. ALWAYS in busy/content-heavy areas and ALWAYS when my memory usage (out of 3GB physical RAM) approaches the 60% mark.
Forgive my inability to use the technical language, but I believe I have reasoned out the problem. I was using 1.19.1.4 and now I use 1.20RC6, btw a much improved interface and all around functionality, but to the issue at hand. I will still 'Crash" out with the same smartheap error, but it only happens when I set my graphics preference to, distance that objects rez in view, to greater than 200, optimum for me is 128. I have as of yet crash with 1.20RC6 and graphics preference 200 or less. I have logged in approximately 10 hours with the new viewer. Naturally the greater the number the quicker the crash occurs.
As a side note things seem to runner faster and objects rez quicker after TP to the sim with 1.20. I hope this helps BTW I run Windows Vista I just got the smartheap library error in 1.20RC6, and this time it was accompanied by an actual real memory leak. This seems only to happen in the Bel Vale simulator, if I don't go to Bel Vale SL's memory use stays below 700 MB. There I've seen it as much s twice that.
no sooner had a posted than i crashed. this time it occured in Viena Sim. I have better luck with 1.20, with respect to i can click ignore and still stay in SL, after several times of clicking ignore I will then crash out of the system, and normally i must wait 5 min or so to log back on. again if i keep my graphics rendering distance small, i am not crashing under normal circumstances.
Why was this closed? This clearly still occurs in versions more recent than the "fix version".
Im using 1.19.4 on a brand new Hp dual core 2 with 4gb memory , and i get this smart heap error after roughly an hour or more, i looked in task manager and sl was using 1.3 gb just about everytime i get the error.
When i start SL up it uses roughly 300mb and just starts climbing and never stops , no matter if im moving or not. If i shut down sl i get the memory back and can run for a few more hours maybe. Real and consistent problem...should be easy to find. On a dead reliable (runs for weeks) Vista x64 3.6Ghz water cooled quad core, 4 GB, 8800GT video.
The error occurs...can get past it for a short while with ignore...once more...nearly always crashes by the third time, sometimes sooner. This is happening on Maching running OS Window XP and Vista as far as I know....Happening in all viewers I have tested so far on my new Acer Machine specs below:
CPU: Intel Core 2 Series Processor (2199 MHz) Memory: 2815 MB OS Version: Microsoft Windows Vista Service Pack 1 (Build 6001) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 7100 / NVIDIA nForce 630i/PCI/SSE2 OpenGL Version: 2.1.2 LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000) Packets Lost: 556/185351 (0.3%) Viewer Digest: 6b1bac12-2a86-e1f2-aa5e-3108db5c8eeb The other 2 machine I have asked if they have a problem are running XP Pro and XP Media OS ...I have noticed more of these error and crashes since the new Server code update this week on this viewer...I went back to this viewer after having this error every 30 mins on the newest released viewer. Don't close this untill it is fixed it is very hard to stay in world with this error ...I am finding more and more people with this error and sending them to this web site . BluesLady Pey Same Problem here I get SmartHeap out of memory Error, then it just crashes out
Toshiba X205-SLI5 This issue should be upgraded to Showstopper on the grounds that it severely inhibits a significant portion of users from experiencing Second Life for any determined amount of time and deserves immediate attention. I would change myself but I would think putting it to a vote would be more prudent.
I just download the newest thing for sl the new release candidate and I am still experiencing the smartheap error I have been for a month now please GET RID OF IT! I am on a windows vista and this has not always been like this but it seems that once the error came it never has gone away
I've had this problem for months on a newish Acer desktop with ATI graphics and it's also happening on my new Dell laptop.
The laptop only came out of the box yesterday le sigh and I managed approx one hour inworld before the smartheap library "out of memory" popup of death occurred. Was the only person on an estate sim. (Pacific Terrace) Dell M1730 This issue needs to be upgraded to showstopper ~ particularly as the latest RC is set to become the main SL viewer. I've been getting this for ages and my searches for the issue were seeming hopeless till today's stumble.
Second Life 1.19.1 (4) Apr 2 2008 11:59:37 (Second Life Release) CPU: AMD (Dual Core) (3013 MHz) Every two to three hours I get the error messages and can at first choose ignore but eventually they pop up so fast after each other I give in or SL crashes on its own. Like Avonlea Graves very frustrated, this has gone on now for ages. I'm starting to get to the point where I can no longer use SL...I can't do my DJ spots if I can't guarantee I can stay logged in and if I am logged out I may not be able to log back in. I could really use that warm puppy round about now. P.S yes this is a showstopper for me in answer to the vote above there. For what it's worth, here is my information:
Second Life 1.19.1 (4) Apr 2 2008 11:59:37 (Second Life Release) CPU: Intel Core 2 Series Processor (2405 MHz) Since this has been an [seemingly ignored] issue for a half a year or more, I'm not holding my breath that anything will happen soon. Makes one wonder if there is anyone minding the store................................... I was EVER SO hopeful when I read the release notes for the newest RC (Version 1.20.11) that I would see a significant improvement in this, but it has actually got MUCH worse. Since logging on to SL this morning at 1am SLT through to now (5.55am) I have crashed no less than 14 times, each time with this error message. It's impossible to use the RC and I've now reverted to my less preferred normal viewer sigh
We are tearing our hair out Lindens, trying to run businesses, do non-profit work, even run exhibits for SL5B, and we can't because of this issue. I agree with the above, it's a showstopper, at least for the RC viewer. The funny thing is SmartHeap is a nearly 20 year old program designed to make it easier to find, manager, and correct memory errors in C and later C++ programs that dynamically allocate memory (in contrast to FORTRAN and COBOL, for those who forgot). That the program has either a memory leak (likely) or excessive allocation (something silly, like allocating memory for each node in a sparse matrix) that hasn't been found yet and even found its way to production at all in (let me check my calendar, 2008, for a second I thought 1992) is surprising.
Salutes Reporting for duty. RC11 has not fixed this, in fact, I don't think it's changed what-so-ever. I don't know how they caused it, a year or two ago it wasn't doing this O_o but yeah, I attached a screen shot with date and time (SLT)
I agree this is noticably worse in 1.20.11. Spend any amount of time at all at SL5B running the RC and you will see it repeatedly.
I'd be looking at texture decompressors and cache management for overflow bugs, guys. I notice that it's not generating crashdumps. Second Life 1.20.11 (90229) Jun 19 2008 21:24:47 (Second Life Release Candidate) CPU: Intel Core 2 Series Processor (2399 MHz) Ummm...I understand how cache management would cause a leak, how would a texture decompresser do it? Is it a home-grown Linden module or a third party?
Funny, I have 1.19.1.4, the supposed fixed release, and i get this about every hour in high traffic regions. Also, if you look it up at the various hardware/software sites, or just Google it, there's a lot for information about it on the web. Many of the reported causes are that the most recent version of MSVCRT.DLL is being replace by an older version, resulting in these errors. That would indicate the SL might be linking in an older version of MSVCRT.DLL in their builds, and is something that should look into. It is becoming a BIG nuisance. I will try replacing my DLL with the latest version, as soon as I back up my system, and post the results.
Just purchased a new computer, and using windlight for the first time ever. Have had the Smart Heap problem daily. I see here that this problem has existed since Dec 07 and has yet to be fixed. If the Fix Pending has been applied on an Internal version, why has it not been released to the public? Why is it taking so long to resolve this issue?
Tory Linden stated back in Feb "From Steve Linden, who's been looking at various bugs of this kind: "This is a dupe of other memory leak bugs. It is now six months later. Can we please be given a Linden update on what is being done to resolve this issue? Intel core 2 duo 8200 - 2x 2.66 GHZ - 6 MB - 1333FSB SL version 1.91.1(4) I have the exact same issue as lordvore voom. I couldn't have explained my situation any better than they have.
After playing SL for a long period of time I'll just get this error for no reason. I have plenty of memory free when it says it. And as emmarie Catteneo said, Tory Linden said that they would be abandoning SmartHeap soon. That was 6 months ago. How long does "soon" mean then? Second Life 1.20.14 (92115) Jul 14 2008 15:20:29 (Second Life Release Candidate) CPU: Intel Core 2 Series Processor (2405 MHz) Second Life 1.19.1 (4) Apr 2 2008 11:59:37 (Second Life Release)
You are at 284602.5, 278630.2, 740.9 in Kolbeinsey located at sim5868.agni.lindenlab.com (8.2.35.170:13001) CPU: AMD (Unknown model) (2410 MHz) Same Problems Screen Pops out with the out of memmory BS!
Can Liden Labs please Fix This BUG! Seriously... how much do I have to pay you guys to fix this. I am not joking! Second Life Release 1.19.1 (4) Ok, so I just built a new computer and I am having this issue now too. I didn't see it on my old computer but I get it constantly now. very disruptive. the only positive thing I can say is it's the only SL bug I get a warning for lol. it happens, I click ignore and log out before I hard crash, though it does crash again as I am logging out every time.
My computer: Information from the Help > About Second Life: You are at 244466.2, 274229.3, 79.0 in Musashi located at sim3322.agni.lindenlab.com (216.82.21.57:13000) CPU: Intel Pentium III/Pentium III Xeon (0.25 micron process) with external L2 cache (3800 MHz) I hope this helps! Please contact me inworld if you need me to answer any questions. happy to help get this awful bug fixed. Very much NOT fixed. - as of this version:
Second Life 1.20.14 (92115) Jul 14 2008 15:20:29 (Second Life Release Candidate) CPU: Intel Core 2 Series Processor (2999 MHz) Okay, time will tell whether this is happening in the lastest 1.20.15 build. I also see the memory leak issue as well and i have 3 gig of ram. However there is a trick that seems to work for every one i encounter, every few min about 10-15 min just minimize the viewer for approximately 15 seconds on my system it doesn't take but 1 second for it to clean up the mess its making in the ram some people it takes longer just depends on the system setup. Why it cleans it minimized i do not know but it works for me and it keeps me from having to re log i am able to stay logged in for hours even entire days if i want to as long as i just minimize it from time to time specially in busy sims as stated. Now i don't know if this will work for every one but it works for me and every one i have encountered.
Has anyone tried running secondlife in full-screen to see if this smart heap error occurs? Just curious since most of the screenshots show secondlife running in window mode.
The last time I recieved this error, I was running Second Life in Vista x64 using window mode. Since then, I've been dual booting into XP and running SL in full-screen (800x600) and I have yet to recieve this error again. If you are running second life in window mode, try and see if full screen helps any. Might serve as a temporary work around for now. Not saying it will, but it's something to at least try. Still happening for me – Please fix this, as it is getting annoying for about 75% of the residents, and even for lindens during office hours. This needs to be fixed! "We'll go to a new memory management system soon" is not an answer, since you're obviously not doing it.
Second Life 1.20.15 (92456) Jul 18 2008 10:58:42 (Second Life Release) You are at 190649.1, 294182.0, 49.9 in Supox located at sim2818.agni.lindenlab.com (216.82.19.61:13001) CPU: Intel Core 2 Series Processor (2671 MHz) Can anyone else verify cade boa's observation (27/Jul/08 10:29 AM)? I can't reproduce the problem on my machine, so I can't try the workaround myself, but I do know that minimizing the window does free memory on my system. If someone else can verify the workaround, I'll have a look at the code to see what's happening.
same problem as described above, crashing every 15 minutes in high frequented environments
prob occured since 3 or 4 month, new quality since update to viewer 1.20 and 2 days ago: it`s no more possible clicking "ignore" and getting a few minutes for restart avoiding hard crash....it spams smartheap library error messages, so you must finish all using the task manager plz Linden Lab fix it Dell machine with Intel Core2 Quad Q6600 2,4 MHz and.....one or two times a day the grafics driver goes corrupt with system message: that it has fixed Still happening in newest client:
Second Life 1.20.15 (92456) Jul 18 2008 10:58:42 (Second Life Release) CPU: Intel Core 2 Series Processor (3000 MHz) Still hapening in Second Life 1.20.14 (92115) Release Candidate or more per say became a bigger issue
CPU: Intel Pentium 4 (Unknown model) (2992 MHz) See aslo: http://jira.secondlife.com/browse/VWR-6851 2008-08-07T07:46:05Z INFO: display_stats: FPS: 7.18 As a test i chenged the RenderMaxVBOSize ( Advanced -> Debug Settings... ) from 32KB down to 24KB and it seems not to crash me no more Perhaps it just for nVidia that would need to be tested but for now i dit not crash me yet and bin loged in for like rather a lot of hours and bin teleporting from sim to sim to test if it would eventualy crash me.
Just had this error on 1.20 too, only switched to it a couple of days ago and I didn't used to get it very often at all on 1.19.1, although I did get very high memory usage and slowness after SL had been running for several hours. Until now the memory usage had seemed a lot better in 1.20, but the Commit Size in Task Manager (which as far as I can see seems to be something like the total memory allocated, including what's been swapped to disk) was right up to 1.7gb when this happened. Actual memory usage was still quite low though (about 400mb). Clicking Ignore on the message seemed to make everything instantly OK again, but I had already been disconnected anyway because SL had frozen for a minute or two before the message came up, and then it came up again in the middle of logging out.
On 1.19.1, I found that minimizing SL actually seemed to make the memory usage worse if anything (on older versions I used to minimize SL whenever I went AFK for a while, but then it seemed to make everything slower when I got back if it had been minimized for a while). Not had a chance to test this properly on 1.20 yet. Side note: Having a high draw distance cause this to happen more frequently.
I'm getting pretty sick of seeing this error. It happens at some of the worst times, and I cant figure out how to avoid it. I've just had it happen yet again, and decided to come check for issues to vote for the fix.
Oh this thread is so familiar.
I upgraded to a radeon 4870 ati card at the weekend and since then i crash every half an hour whereas before with my 8800gtx solo it happened every 3 to 4 hours when i was using chat. I wouldnt dare go near chat at the moment. Operating System: Vista 64bit service pack 1 Every time it crashes it resets almost everything back to default as well, which is really really annoying. xx this drives me nuts when the hell is this going to be fixed i swear if this isnt fixed by the next client / server/ viewer w/e thingy im going to be severely pissed cause this is a annoying bug to get constantly and makes sl impossible to play
I had this trouble for the first time today "Smartheap Library out of Memory". I was at Lost City of Angels when it happened. I started lagging very bad first befor the message and when clicking retry or ingnor the messege kept coming up. I logged off and havent been on since...thought Id investigate the trouble first. It a new laptop and Iv only been running sl on it for about 2 months. I also only turned nearby lights on today for the first time, I didnt befor thinking it may affect lag. I have a Dell XPS M1530 with NVIDIA GeForce 8600M GT with 3GB of memory and 1.7 GB remaining if that is any help. I hope not to have this problem very long, if you can, PLEASE HELP!!!!!
I also was in City of Lost Angels, when this happened, info on rig to follow
SL ver 1.20.15 (92456) OS: Win XP SP3, 4GB RAM DDR2 "Read as 3.25GB' VPU: ATI Radeon HD3400 Series Ive been having this issue for a long time too.. 4 or 5 times a day the sl console comes up then i get smartheap library prompt.. i contacted live chat and they told me to unmark the sl consoles to stop it coming.. i checked and didn't have it marked in the first place..it always popped up before the shl.. Anyway I have downloaded the new sl update and have had no errors so far today 27th September.. Been on for a few hours now and nothing..so fingers crossed they have fixed it!
Second Life 1.20.16 (97603) Sep 24 2008 18:30:45 (Second Life Release) Operating System: Windows Vista™ Home Premium (6.0, Build 6001) Service Pack 1 Pulling together what appear to be the pre- (1.20 and below) and post- (1.21 and above) SmartHeap symptoms.
I am also having the smartheap ...out of memory issue. I first had this error on the older viewer (many times) and now i have had this error message twice with the new viewer 1.20.17
At the time i get the error message i have NO other programs running and I am NOT in a busy or crowded place. I have a new ACER desktop media center, 4GB RAM, NVIDIA 8600, Quad-Core. If anyone has any suggestions on how i might fix this problem , It would be greatly appreciated. : ))) I'm checking on the status of this project.
Those of you getting this issue in 1.20 and 1.21: Please check the hardware option of the graphics setup - do you show an unrealistic amount of video card memory?
@ Soft Linden – you mean the setting for the Texture Memory?
I checked in graphics setup and found that the video card memory was set to use 512MB. I have a 1GB video card. I started getting this 'out of the blue'. No specific event like upgrading viewers that I can associate it with. Hadn't installed any new programs. It has been happening with the last 3 viewers - including the newest. ******* CPU: AMD (Unknown model) (1808 MHz) ok this is what I use can anyone tell me how to fix this stupid smart heap library memory error I have been dealing with this for 3 months now! non stop!
I have been dealing with this for months. No matter what my graphic setting are and there doesnt seem to be a specific event that causes it. DOesnt matter the viewer, tho it seems to be happening more with the latest release as well as the new RC. "I should be hitting 'out of memory' anytime now' has become a standard line for me. Its getting old.
O S: Windows Vista™ Home Premium - Service Pack 1 Maggie:
I read through your problem, this is also happening to me, but not just this. SL crashes/closes so excessively that I've given up for now. It's not a specific viewer, but all different viewers I've tried including: Regular SL, RC Client, and Onrez. I'm having the same problem as well, and my specs are: 500GB HD, 4GB Memory, 2.53 Dual Core Processor, running on Vista 64-bit. Any suggestions? Should I get the release candidate and that will fix it?
Thanks! I have been experiencing this issue since long time. Just like the others.... busy places, music, lots of details around, zooming far distances... all cause the smart heap out of memory thing.
The thing is that, thousands of people face this problem and hundreds of forums talked about it. The conclusion is ONE!! Linden Labs, until this day, could NOT release a decent version of SL that does NOT leak your RAM. It was never a graphic card issue, it is always a memory leak. If you are using VISTA, try enabling the memory gauge in your sidebar and monitor the increase of RAM while using SL especialy in busy places. How to solve it?????? One temporary solution if you do not wish to log out and in again is to minimize the SL window for few minutes. This will give you a chance of 2 to 5 minutes to finish what you have in hand and then it will start poping like hell again till you completly logout. The other solution is... You need more RAM in your system BUT remember, if you are using a 32 bit operating system like Vista or XP 32 bit then forget about it cause both of them CANNOT read more than 3.6GB of RAM even i you have a 1000GBs installed. The thing is, those buttheads at Microsoft thought they can fool us by releasing SP1 for Vista where it actualy tells you what exactly you have as RAM in your system but it does NOT use them all. It again uses 3.6 of it and I have done the tests. I have dicussed this with some Microsoft people who finaly agreed to replace my 32Bit with 64Bit to solve this problem since I bought my system with 6GB RAM. I need to remind you that NOT all your hardware components and application can run on 64Bit so this is the bad side of it. In the meanwhile, Linden Team, you may continue to remain silent and unable to answer anyone on this thread or any other thread and pretend that you are trying to investigate the issue as if it is a new issue! While you guys are NOT good at anything but charging us for the premium and allow other residents to rip us the way they like with no protection from your side but your famous statement "we do not solve residents disputes". Sigh This problem is just like the voice problem for many people who has no issues with their VoIP with any other application but SL and Linden Team CANNOT do anything about it. I like the game of SL but I really feel that every $ we spend in SL is not worth the lousy support and efficiency of your application that's all I have to say for now. Guys... it is a hopeless case unless you want to convert your system to a 64Bit and do a lot of changes and sacrify a lot of none-compatible 64Bit drivers for the sake of playing.... Second Life. This issue came up at the opensource meeting yesterday and was discussed for an hour. Apparently it can't be isolated to a single cause, this doesn't mean it isn't being worked on. Transcript is posted here for the curious.
http://wiki.secondlife.com/wiki/Open_Source_Meeting/2008-10-16 I took the lastest SL upgrade friday, 10/17/2008. The 1-21-6 version..All of a sudden since i took that upgrade i no longer get the OUT OF MEMORY message anymore and dont have to reboot..I used to get the OUT OF MEMORY about every 3 hours and now im on for 8 hours and longer and i dont get the message any longer..Fingers r crossed..
 )))). Could it be???????????????????? Or am i dreaming???..LOL I also took the new upgrade on Friday.. 3 days no smart heap errors..woohooo..
/me whispers quietly, "I haven't seen any of these errors since I upgraded to Second Life 1.21.6 (99587)"
/me slips out quietly, giving a smile and a thumbs up to the Linden team - knocking on some wood as I go..... (Now if NVidia would come up with a better driver or something.... Driver crashes occasionally on SL. Don't know if it's anything to do with this memory leak issue or not.) I'm not complaining that i no longer get the, OUT OF MEMORY message. As a matter of fact its about time this 2 year old issue is, i HOPE finally fixed. So we dont have to ASSUME that this latest upgrade WAS the fix, i just wish that someone from Linden Lab would at least have the decency to at least SAY something in this forum to all of us and tell us was it, or was it not the upgrade that fixed this??, or is this just a temporary glitch that is correcting this problem??????????????????????????????????????/ Thank you.
@alan: This isn't a single specific bug. That message is displayed when running out of memory, regardless of the source of the leak.
Several memory leaks were fixed in 1.21 (and in 1.20, and in 1.19...). Whether it was the leak that was causing the problem in your case is hard to say without a lot more information. @Soft Linden
Thank u for ur responce. I do appreicate it. Im not sure what u need but heres my PC specks information. Is this what u need?
Gateway fx4710 64bit- operating system ps @Soft..It was the smart heap Library out of memory i was getting.
I did a quick survey of some of the people who commented on this problem on whether the problem was fixed for them in 1.21.6. Two said yes. One said it got better. And one said it got worse. That's progress for most. But it indicates that there was more than one problem. And they're not all fixed yet.
For me, its worse.... I still get the out if memory error, tho now sometimes the client just goes 'poof' and closes out on me. I have other various issues, too like slow texture loading.
Further to my earlier comment...
I received my 64Bit Vista. Unlike what many says about it, it is a fantastic OS, everything is running smooth and no conflicts. As for SL.... I played more than 8 hours, music, videos, crowded places etc.... No error so far. Glad this is happeneing. and I still did not get the latest version of SL. This proves what i said earlier..... you need at least 4GB available to cover the leak SL causes and you need Vista 64Bit to handle more than 3.4GB RAM The question is, can everyone afford financialy and technicaly to use the 64Bit system to play SL with no hassle? @alan itano hmmmmmm
I just noticed some of the people who posted comments here have even higher specs than what i have like 8GB RAM and they use 64Bit OS and good VGA Card and still they get it. This made me re-evaluate the issue again and somethign came accross my mind..... HOW MANY OF YOU GUYS HAVE REALTEK NETWORK CARD EMBEDED IN YOUR MOTHERBOARD? I upgraded the driver of mine during the system upgrade to 64Bit. This may be yet another factor too! @Cadd Carter
Ever since i took the lastest viewer upgrade, 1-21-6 version, a few days ago, i NO longer run out of memory..Now i've been on for as long as 12 hours straight without an OUT OF MEMORY eror Well I have to reconfirm. Using a 64Bit Vistal solved the issue once and for all! This is only due to the fact that no matter how much SL is leaking memory, i still have more since Vista 64Bit can read all of the 6GB i have on my machine.
Bad luck for 32Bit users.... no matter what you do, you will still have SL eating up your RAM since 32Bit can read only upto 3.6GB from your Physical RAM no matter what. And of course. Linden Labs will remain silent. They cannot fix this bug, nor the voice bug, nor also can they fix the recent new bug realted to clotings and how they ask people to roll back their drivers to older version!!! Vista x64 is not a solution in itself... Cadd is right in that 64 bit operating systems allow a larger address space (up to 128+ GB for Vista Ultimate x64)... but as long as SL fills up your memory, then the problem might occur regardless how much memory you have. Granted, the odds of getting an "out of memory error" is greater in windows 32 bit since it restricts any application from allocating more than 2GBs of memory.
I don't see why the SL Viewer would need more than 2GBs of memory and it's probably not assuming it has an unlimited amount either... But who knows, they might not be able to fix this problem (especially if they can't replicate it)... If anything, this bug has brought some much needed attention to the overall stability of the viewer... I'm getting SmartHeap error messages too. and the computer crashes. i'm not a geek, but this is what i have:
Gateway laptop-Windows XP Pro SP-2 Processor x86 Family 6 Model 13 Stepping 6 GenuineIntel ~1694 Mhz Total Physical Memory 1,536.00 MB Available Physical Memory 1.04 GB Total Virtual Memory 2.00 GB Available Virtual Memory 1.96 GB System managed Virtual memory i think the problem is video. only have 32 mb video memory on the motherboard. any thoughts, or ideas? beside a newer laptop? (desktop is not viable) The later issue VWR-8841 is marked Fix Pending re RC Viewer 1.22
Please would reporters of this issue try the latest RC Viewer which can be downloaded from here Release Candidate Test Viewers If you still have an issue, please reopen [left sidebar] and add your full computer environment, Help > About Second Life, including the Viewer you are using and the Region(s) where you have this issue. Please also include the Graphics Card driver version you have. For technical, time-sensitive and/or Region/Account specific issues please Submit a Ticket with Support Thank you : ) |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Critical
Out of Memory in Smartheap Library errors
About 2GB of my 3GB of physical RAM was in use at the time - this seems to be a critical borderline anyway, I usually simply crash to the desktop without warning if I approach that kind of memory usage. (Why SL doesn't make use of the remaining gigabyte of free RAM is beyond me, and I'm running WinXP Pro SP2 with the /3GB boot option enabled.)
I ended up clicking 'retry' a few times which only kept bringing it back up. Clicking 'Ignore' allowed SL to run for a few more seconds before the error window showed up yet again. I clicked Ignore a second time, attempted to detach HUD objects and move to a quieter place as quickly as possible, but within moments SL crashed with an error message given by the MSVCRT runtime library (unfortunately I don't recall what it said, but it also complained about an out-of-memory issue).