Cannot print exception string because Exception.ToString() failed.

Marc Clifton

hahahahaha. Never seen that one, and no, I don't have a custom exception handler.

Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework

PIEBALDconsult

How about ((Exception) myException).Tostring() ?

Steve Raw

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". :laugh: Another one I've seen reads: "Keyboard Not Found. Press F1 to Resume". :laugh:

raddevus

Is it .NET Core? Exception.ToString() failed. · Issue #5203 · dotnet/runtime · GitHub[^]

CPallini

All my life waiting for that happen!

"In testa che avete, Signor di Ceprano?" -- Rigoletto

Marc Clifton

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.

Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework

Marc Clifton

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!

Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework

Marc Clifton

Nope, plain .NET 4.7.2. I think it's related to Dapper blowing up in a bad way, lol.

Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework

jschell

In Java/Net you can get an out of memory error for reasons other than the totality of memory that exists for the application.

BernardIE5317

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"

jschell

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[^]

RickZeeland

I think it's exception-al :-\

TNCaver

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)

jschell

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.