Well, once again.. the battle of OSS and Microsoft. World is waiting for the time when OSS guys stop pointing fingers towards the MS products.
According to me, Non-MS products like linux also generated errors.. doesn’t it?? then why does it never surface out??
reason 1: its only used by those, who choose to tolerate it…
reason 2: maybe the percentage of the users who use ms products is far greater than non ms product users… so chances of gettin an error is also more with ms products….
however, coming back to the topic…
the snap here shows an internal error, caused by another internal error message box.
the point to be noted is….
1. the application concerned is the Eclipse SDK, an OSS.
2. it is developed in an OSS language, Java, considered to be platform independent
3. whole world knows that Java has its own memory management engine. MS can’t intefere.
4. heap memory is something a program should reserve for its own good at its own start.
Now, an error of low heap memory if popped is cuz of the programmer’s mistake.. not OS. cuz os always give u the chance of having more Memory. And programs which consume humongous memory are also present. Good example: adobe photoshop, runs fine on windows…
Well, I dont want to generalise this error completly on OSS products…but here, the only essence of MS is the operating system, which in no case responsible for the eror
OSS guys never said or claim anything to be perfect.. so the “pointing finger” issue never creeps in :).
Contrary, MS guys bullshit that they deliver best product and a user knows how “best” they are, and hence all the fingers point in one direction.
The application concerned is Eclipse, you are right, but it was not always an OSS :), which means that it’s seen both the world ;).
Now coming to the error, it’s quite straight forward, it’s apparent that its a “heap memory” prob. Now even before we get into a discussion here, let me point out a few pointers, then you can put in your comments :-
A pointer to an object of one data type will in general have a different value than a pointer to an object of a different data type, even if the objects are stored at the same physical address. Pointers have strict alignment requirements, and it is not always possible to coerce the type of a pointer.
The pointer is used in subsequent procedure calls to refer to the allocated memory. The Mem[] construct is used to access the data. When passed to a procedure, the data are treated simply as an array. (this is basics of what happens, or calls are made to blocks of data or more commonly known as “heap”)
This is handled my the underlying OS, as far as I know, you can correct me if I’m wrong here. If I’m wrong, then it’s not OS issue, if I’m right, then you know who’s got the issue right :P..
Just type in “out of memory error” in google and the first two links will point to articles which state how you can over come it, from the microsoft support links .. so this means that its not Eclipse which caused the error right
~G
Well, once again.. the battle of OSS and Microsoft. World is waiting for the time when OSS guys stop pointing fingers towards the MS products.
According to me, Non-MS products like linux also generated errors.. doesn’t it?? then why does it never surface out??
reason 1: its only used by those, who choose to tolerate it…
reason 2: maybe the percentage of the users who use ms products is far greater than non ms product users… so chances of gettin an error is also more with ms products….
however, coming back to the topic…
the snap here shows an internal error, caused by another internal error message box.
the point to be noted is….
1. the application concerned is the Eclipse SDK, an OSS.
2. it is developed in an OSS language, Java, considered to be platform independent
3. whole world knows that Java has its own memory management engine. MS can’t intefere.
4. heap memory is something a program should reserve for its own good at its own start.
Now, an error of low heap memory if popped is cuz of the programmer’s mistake.. not OS. cuz os always give u the chance of having more Memory. And programs which consume humongous memory are also present. Good example: adobe photoshop, runs fine on windows…
Well, I dont want to generalise this error completly on OSS products…but here, the only essence of MS is the operating system, which in no case responsible for the eror
OSS guys never said or claim anything to be perfect.. so the “pointing finger” issue never creeps in :).
Contrary, MS guys bullshit that they deliver best product and a user knows how “best” they are, and hence all the fingers point in one direction.
The application concerned is Eclipse, you are right, but it was not always an OSS :), which means that it’s seen both the world ;).
Now coming to the error, it’s quite straight forward, it’s apparent that its a “heap memory” prob. Now even before we get into a discussion here, let me point out a few pointers, then you can put in your comments
:-
A pointer to an object of one data type will in general have a different value than a pointer to an object of a different data type, even if the objects are stored at the same physical address. Pointers have strict alignment requirements, and it is not always possible to coerce the type of a pointer.
The pointer is used in subsequent procedure calls to refer to the allocated memory. The Mem[] construct is used to access the data. When passed to a procedure, the data are treated simply as an array. (this is basics of what happens, or calls are made to blocks of data or more commonly known as “heap”)
This is handled my the underlying OS, as far as I know, you can correct me if I’m wrong here. If I’m wrong, then it’s not OS issue, if I’m right, then you know who’s got the issue right :P..
~G
One more thing ,
Just type in “out of memory error” in google and the first two links will point to articles which state how you can over come it, from the microsoft support links .. so this means that its not Eclipse which caused the error right
~G