+972 52-548-6969
No, Alanis, THIS is ironic
time to read 1 min | 44 words
This is what I got when I was trying to figure out an OutOfMemoryException in RavenDB
FUTURE POSTS
- RavenDB on AWS Marketplace - 16 hours from now
- Production postmortem: The race condition in the interlock - 4 days from now
- When racing the Heisenbug, code quality goes out the Windows - 6 days from now
- Pricing transparency in RavenDB Cloud - 8 days from now
- Who can cancel Carmen Sandiego? - 11 days from now
There are posts all the way to Apr 14, 2025
RECENT SERIES
-
Production Postmortem
(52):
12 Dec 2023 - The Spawn of Denial of Service -
RavenDB
(13):
02 Apr 2025 - .NET Aspire integration -
RavenDB 7.1
(6):
18 Mar 2025 - One IO Ring to rule them all -
RavenDB 7.0 Released
(4):
07 Mar 2025 - Moving to NLog -
Challenge
(77):
03 Feb 2025 - Giving file system developer ulcer
RECENT COMMENTS
-
By Pierre on Introducing Rook AI
-
By my blog on Optimizing by 170,000%(!) by not being silly
-
By Oren Eini on Optimizing by 170,000%(!) by not being silly
-
By John on Optimizing by 170,000%(!) by not being silly
-
By Oren Eini on Optimizing by 170,000%(!) by not being silly
Syndication
| Main feed | |
| Comments feed |
Comments
I'd think you need a full reboot :o)
No, Ayende, THAT is ReSharper.
:)
no, the real irony here is the Ants Memory Profiler ad that i'm seeing on the right-side of this page right now :)
The new ants UI is great, but the program is slow and buggy as hell. I get much better results from JetBrains product.
That is EXACTLY what my experience was the one time I tried to use JetBrains' memory profiler to figure out an OutOfMemory issue. I thought it was funny - and useless. The performance profiler works great, though.
Had similar experience a few years ago using the jetbrains memory profiler. Have a look at yourkit .net profile, it handles things much better.
Why do people try to fix OutOfMemoryException? Isn't it obvious that they only need to add some more memory.
Also, the name 'OutOfMemoryException' is a bit misleading. You can get the exception even if you have available memory. A better name would be CouldNotAllocateMemoryException.
Smart guy, more memory dont resolve the problem.
First because you can say this to Your client
Anyway it won't work, this exception mean that don't exists continuous memory space at virtual memory
The Jetbrains memory profiler has been immensely useful to me to clean out all the garbage of dangling references off static events, funny garbage collector handles, misbehaving 3rd party UI and OOMs due to running out of GDI objects and what not in a Winforms App. Irony or not, it can be a pretty useful tool.
@Erik - What's it have to do with resharper?
@Fujiy: Never heard of ironic? I think smart guy is just trying to be funny. :)
BTW: I think ANTS Profiler and Jetbrains Profiler are both excellent products. Both helped me a lot.
@NC - I looked at the stack trace and saw ReSharper, which sync'd with my experiences with tool. I should have generalized to say 'JetBrains' instead.
I was only kidding anyway. I love JetBrains tools when they aren't starved for RAM.
Seen this as well. Too bad they don't have an x64 version.
@Erik - OHHH I only saw JetBrains, didn't see resharper in it.
Oh, wait, looks like they DO have x64 version now. This should help.
That's why you should switch to Telerik JustCode. I've been using it since the early betas and love it WAY more than ReSharper or CodeRush. :)
Comment preview