Debugging pain
-
An intermittant problem that shows up only when you're writing code at home, not at work. Crashes hard at home with all kinds of OutOfMemory failures, but the machine isn't out of memory or resources at all. Not even close. After 5 hours of fruitless debugging, the painful part is where you facepalm yourself hard because you just realized that in a Parallel.ForEach your using around an I/O bound problem, you forgot to cap the number of threads it can create! The process bombed out at about 600 threads. :doh: Whoops!
A guide to posting questions on CodeProject
Click this: Asking questions is a skill. Seriously, do it.
Dave Kreskowiak -
An intermittant problem that shows up only when you're writing code at home, not at work. Crashes hard at home with all kinds of OutOfMemory failures, but the machine isn't out of memory or resources at all. Not even close. After 5 hours of fruitless debugging, the painful part is where you facepalm yourself hard because you just realized that in a Parallel.ForEach your using around an I/O bound problem, you forgot to cap the number of threads it can create! The process bombed out at about 600 threads. :doh: Whoops!
A guide to posting questions on CodeProject
Click this: Asking questions is a skill. Seriously, do it.
Dave KreskowiakDave Kreskowiak wrote:
Whoops!
Every great developer has said that before. It's the terrible developers that never say that either because they don't know when they screw up or they won't admit it. :-D
There are only 10 types of people in the world, those who understand binary and those who don't.
-
An intermittant problem that shows up only when you're writing code at home, not at work. Crashes hard at home with all kinds of OutOfMemory failures, but the machine isn't out of memory or resources at all. Not even close. After 5 hours of fruitless debugging, the painful part is where you facepalm yourself hard because you just realized that in a Parallel.ForEach your using around an I/O bound problem, you forgot to cap the number of threads it can create! The process bombed out at about 600 threads. :doh: Whoops!
A guide to posting questions on CodeProject
Click this: Asking questions is a skill. Seriously, do it.
Dave KreskowiakWhoops :doh:
In code we trust !
-
An intermittant problem that shows up only when you're writing code at home, not at work. Crashes hard at home with all kinds of OutOfMemory failures, but the machine isn't out of memory or resources at all. Not even close. After 5 hours of fruitless debugging, the painful part is where you facepalm yourself hard because you just realized that in a Parallel.ForEach your using around an I/O bound problem, you forgot to cap the number of threads it can create! The process bombed out at about 600 threads. :doh: Whoops!
A guide to posting questions on CodeProject
Click this: Asking questions is a skill. Seriously, do it.
Dave KreskowiakWe have an application that automates the running of other applications we have that take data feeds from clients and process them. Automation uses a command line to kick of the different processing programs. All of the sudden the automation starts logging an error even though the processing completes successfully. I finally track down the location of the line that is recording the log message. The code in automation scans the log file of the processing program for the string "error" and reports if it finds it. I look through the log files of the processing programs and everything looks normal, no errors being reported. After several more reports of this problem I am looking at the log file again and I finally find the cause of the problem. The file services people who manage the automation process wanted more detailed logging, to include recording the command line parameters being used for each different run of the processing application. One of those command line parameters is used to turn on and off message/error logging. The message sent to the log file for the logging switch said, "Command Line Parameter to log errors" WHOOPS! :-O Yes, I added that code.