|
Steve Raw wrote: How can you possibly refute photographic evidence? That's a good one!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Steve Raw wrote: How can you possibly refute photographic evidence? Because it is not photographic evidence, it is a constructed image. Maybe you should stop smoking whatever it is you are on.
|
|
|
|
|
Richard MacCutchan wrote: Because it is not photographic evidence, it is a constructed image.
Everyone knows that if it's on the Internet, then it's true.
How do you not know that?
I get the feeling that people aren't taking my experience seriously.
|
|
|
|
|
Steve Raw wrote: Everyone knows that if it's on the Internet, then it's true.
And he said 'Because it is not photographic evidence'.
On the internet.
So that is true.
|
|
|
|
|
Mike Hankey wrote: Welcome to Ward B
I find that to be ridiculous!
...
Ha. You're crazy!
modified 15-Dec-23 16:55pm.
|
|
|
|
|
Hah. You should see what's going on in Ward C!!!
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
k5054 wrote: what's going on in Ward C
Don't you go there, girlfriend!
|
|
|
|
|
Not to mention the place, not even a Ward, that must not be named.
|
|
|
|
|
Hmm .. I am in doubt, is it about procrastinating or about something else ...
|
|
|
|
|
peterkm wrote: Hmm .. I am in doubt, is it about procrastinating or about something else ...
Yes... Now that you mention it, I think there just might be some sort of connection there...
modified 15-Dec-23 19:20pm.
|
|
|
|
|
hahahahaha. Never seen that one, and no, I don't have a custom exception handler.
|
|
|
|
|
How about ((Exception) myException).Tostring() ?
|
|
|
|
|
I'm not throwing the exception -- I think it's Dapper and I think it's related to "out of memory" even though I have plenty.
|
|
|
|
|
In Java/Net you can get an out of memory error for reasons other than the totality of memory that exists for the application.
|
|
|
|
|
I've seen out of memory errors when it was actually a full disk drive. Not with Dapper, but with other scenarios.
There are no solutions, only trade-offs. - Thomas Sowell
A day can really slip by when you're deliberately avoiding what you're supposed to do. - Calvin (Bill Watterson, Calvin & Hobbes)
|
|
|
|
|
Ah yes!
I had forgotten about that. I saw that with a Java app.
The OS Virtual Memory was mapped unto the same drive/folder where the application log was being written. So after the log had been writing for a while there was no more virtual memory. Delete the logs and the problem goes away. Quite annoying and unexpected problem.
|
|
|
|
|
Ha! That's funny. What language are you programming in?
One of the funniest exception messages I've seen reads:
"Out of memory: Kill process, score, or sacrifice child".
Another one I've seen reads:
"Keyboard Not Found. Press F1 to Resume".
|
|
|
|
|
C#.
And yeah, "sacrifice child" is rather novel! I remember seeing those "keyboard not found. Press F1 to resume" messages in old DOS systems. Those were the days!
|
|
|
|
|
|
Nope, plain .NET 4.7.2. I think it's related to Dapper blowing up in a bad way, lol.
|
|
|
|
|
All my life waiting for that happen!
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
the exception message in case of my own coding error reads "internal error apologies if computer exploded please do not take legal action as am saving pennies to purchase Magnum Dynalab/VTL/Harbeth/ATOHM/Shunyata Research system"
|
|
|
|
|
The general problem is that one can get an out of memory problem even when there is seemingly plenty of memory for the application.
I believe this can happen in Java. [Edit] (See other post - it can happen on Java.)
I know it can happen in .Net.
For .Net it happens when the Large Object Heap runs out of memory. I think there can be other cases as well.
Now why would that matter for the code given? Because the string it attempts to build would result in an object that would go on the Large Object Heap.
In my experience I saw this when the application was doing a lot of transfers of files by using in memory copies of the files between different layers. Due to over generalization of course. Insisting on passing streams between layers and then each layer copied the stream into memory and it went down the chain. Then when one adds threads to that it starts chewing up memory.
In terms of the Exception class (or children) I have seen layers that caught an exception, then used that exception stack trace to create the message for the Exception that it threw. Which might be useful and even required if going over the wire it will lead to very large Exception messages.
The Large Object Heap cutoff is the rather odd number of 85,000.
[Edit] - Java example post
The Lounge[^]
modified 18-Dec-23 12:47pm.
|
|
|
|
|
I think it's exception-al
|
|
|
|
|
I had a smart guy tell me this, so I'm sharing it. The next time some dude on CP wants to tell you that Fahrenheit is dumber than Celsius because it goes by the boiling point of water.
Two things to note:
- The boiling point of water is different depending on your elevation. So, that's not a holy grail metric like people claim.
- A predominate theory of Fahrenheit was that it was created to be more people centric. As in 100 is close to average human body's temp and zero means you're in serious trouble.
Just because Fahrenheit's boiling point of water at sea level is 212 doesn't make it dumber. It means people insult things they know little about.
Jeremy Falcon
|
|
|
|