C# Memory Leak Torpedoed Princeton's DARPA Chances 560
nil0lab writes "In a case of 20/20 hindsight, Princeton DARPA Grand Challenge team member Bryan Cattle
reflects on how their code failed to forget obstacles it had passed. It was written in Microsoft's C#, which isn't supposed to let you have memory leaks. 'We kept noticing that the computer would begin to bog down after extended periods of driving. This problem was pernicious because it only showed up after 40 minutes to an hour of driving around and collecting obstacles. The computer performance would just gradually slow down until the car just simply stopped responding, usually with the gas pedal down, and would just drive off into the bush until we pulled the plug. We looked through the code on paper, literally line by line, and just couldn't for the life of us imagine what the problem was.'"
I'll show you mine if you.. (Score:4, Funny)
Well, there's your problem! (Score:5, Funny)
Categorization of Resource Management Issues (Score:4, Funny)
Background:
There are more types of resource leaks than just memory leaks. A memory leak is when your program keeps hold of memory it's not using. An object leak is when your program keeps hold of objects it's not using. A file descriptor leak is when your program fails to reuse the descriptors for files it has closed and will not reopen. Many other types of leaks could be considered.
Exercises:
1. Determine which issue this scenario describes.
2. Figure out which issue can be handled by automatic memory management.
3. Discuss whether, and if so why, the answers to Exercises 1 and 2 mean there is some conceptual discord between the wording of the scenario and the use of the term "memory leak".
Re:Friends do not let Friends use Windows and Driv (Score:5, Funny)
Nothing new here move along....OH Wait? (Score:2, Funny)
Re:As a C kernel programmer... (Score:5, Funny)
Re:Well, there's your problem! (Score:5, Funny)
Re:Well, there's your problem! (Score:5, Funny)
Perpetual motion machine vendors (Score:5, Funny)
I was working at a coal-fired power plant which needed a new pollution control device before 2010. There, I would dig through the literature, and try to find suitable products and operating conditions for this device. Anyway, this involved a lot of meetings, conference calls, and business lunches with the suppliers in question.
Then there was Joe.
Joe was our Alstom sales rep: portly, humorless, slow to speak and slower to understand. He was also a devote Utahnian.
Well, one day, we were killing time while waiting on a conference call, my supervisor left the room, and we started talking about universities. Then he dropped the bomb:
"In my Senior year, I worked on developing perpetual motion machines."
My supervisor then reentered the room, and we got back to work. I felt like I'd just seen a dancing frog.
Re:Well, there's your problem! (Score:3, Funny)
Re:I'll show you mine if you.. (Score:5, Funny)
Re:Well, there's your problem! (Score:4, Funny)
Re:I'll show you mine if you.. (Score:1, Funny)
Re:Not a C# fault (Score:1, Funny)
Re:I'll show you mine if you.. (Score:3, Funny)