Content Browser causes crash?

[ctalkep]

I can have the content browser open, but after I use it a bit (search, scroll, clear, etc.) It freezes. Except instead of just freezing UDK, it has a nasty habit of completely freezing my computer. Once this happens my whole computer is unresponsive for a few minutes. Help?

[Coin-goD]

http://forums.tripwireinteractive.co...ad.php?t=74907

[Srinidhalaya]

I needed 16gigs RAM to prevent my entire computer from freezing when SDK crash occured. 8gigs ran it just fine, but couldn't handle the crash.

Also, use listview instead of thumbnail preview, and also right click on "external" and load all assests, multiple times until the option is greyed out.

[ctalkep]

Yes, I found that sticky right after posting, much to my embarrassment.
And, yeah I've been using list view, it's a little bit more "Guessy" but it'll get the job done. I have 8gb of RAM exactly. But apparently it likes to use all of that! So since I have upgrades planned anyway, I'll just have my guy throw in a few RAM cards. Thanks for the help!

[Srinidhalaya]

I upgraded to 32gigs (not really nessisary), and when it crashes, the ram usage shoots up to around 68%-75% before it drops down to about 40% and back up to 68%-75%, over and over, and I have to manually close it. So having 8gigs can be a bit under resourced when the typical crash involves up to 24gigs in memory leak.

Actual performance in the SDK doesn't have a noticable change above 8gigs, but during a crash its the difference between a hard reboot, vs program not responding.

This drove me nuts for 3 months...

[Coin-goD]

That's weird, I have only 4GB of RAM, and when it crashes it dosn't freeze my PC.

You should close everything you don't need (even things hidden), make the Editor top priority and use a WinClassic theme.
With this I don't even get much crashes. Altough I struggle a bit (Lag on big maps).

I'm getting an extra 4GB mem soon, but as you can see you have a really weird problem.

[Srinidhalaya]

When I had 8gigs, and computer froze, SDK was the only thing running. With the way the ram suddenly stacks up, it wouldn't matter what was running or not, it crashed. Upgrading to 16 immediately stopped the hard crash, and reduced it to "program stopped working". I only went for 32 because the 16 was borrowed from my wife, and I had to "One Up" her.

This specific crash isn't doom and gloom. Its quite manageable, and practically avoidable. It's specifically related to the search function in the content broswer, and can be easily reproduced by several different people and computers. I would consider yourself very fortunate, with the results you have.