current community

your communities

more stack exchange communities

Stack Exchange
tour help
up vote 6 down vote favorite

This concerns this currently deleted question.(*) My opinion is that a program getting out of memory after 3 hours is basically working. It may not be good enough for what's required, but it's exactly as broken as a code too slow for what's required. In the first case you see a crash, in the second you see it running "forever".

With smaller requirements it may work well. It's not fundamentally broken, it's just not good enough.

There may be a bug causing this, but we can't tell it without reviewing it first. I tried to vote to undelete, but it's a moderator's decision.

(*) This question has been basically copied to SO.

share

2 Answers 2

up vote 11 down vote accepted

In my opinion, programs that run out of memory with large inputs are in the spirit of Code Review (assuming that everything else about the question is OK). Performance and scalability are among the key concerns we frequently address. I don't see running out of memory as much different from — they are related problems in the space-time continuum. Since we allow questions, we should also allow questions about where the program runs out of memory.

That said, the author of the question should make some effort to demonstrate that the program works correctly with small inputs, and the question should be primarily about improving the code, not about how to tweak heap size settings. That configuration issue was best addressed on Stack Overflow. I deleted the question on Code Review since the author cross-posted it on Stack Overflow.

I've undeleted the question on Code Review and edited it to put the focus on the code rather than the configuration issue.

share
    
Thanks for undeleting! The problem with the SO question is that the OP initially didn't understand my comment concerning eclipse.ini, so I repeated it there... and the chance to get an answer on the real problem got lost. –  maaartinus Jun 20 at 5:39
up vote 2 down vote

Note: I can not read the question, so my answer is based on the information given by the OP.

Code on CodeReview should work to the best knowledge of the OP. If the objective of the code is to handle 500 kB at most but the code crashes at 2 GB, the code is considered working. If those are reversed, it isn't.

Non-working code should not be posted. However, often it's a design flaw causing the lack of extendibility of the code. If the code can be redesigned to be extendible, the 'non-working' part of the code is no longer a problem.

In my opinion it's a grey area. The decision should be made based on the wording of the question and perhaps even on the amount of cooperation given by the OP when confronted with the problem.

share
1  
Now it's undeleted. The objective is usually pretty subjective: It does what I wrote it for and now I want more. Or the other way round. +++ I wouldn't consider the wording important as it can lead to punishing honesty. –  maaartinus Jun 20 at 5:44

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .