opening a new project opens led blink example

[C_Moore]

Hello Everyone,

This just started happening. If I open a new project in the IDE then the led blink example opens instead on a blank page. Has anyone else seen this?

Hi, its great to see you visiting our forum. Why not try Proton Compiler for FREE? Download the FREE version of Proton Compiler, Its called Amicus18 and its available from HERE Already using proton Compiler??? Get rid of these pesky messages... get LICENSED USER STATUS

[C_Moore]

OK I closed down the IDE and reopened it and it works as it should now. I had left the IDE open for 2 days.

[normnet]

OK I closed down the IDE and reopened it and it works as it should now. I had left the IDE open for 2 days.

I have seen similar occurrences with PC programs left running especially as the PC's become older.
I'm no computer tech but would this have to do with the PC's ram refreshing hundreds of times per second, each refresh reading a bit of data voltage and if above a given point it is rewritten to to recharge it's voltage to maintain until the next refresh?
Maybe the data on the ram becomes corrupt after thousands if not millions of refreshes?
I believe closing the program takes it out of RAM until it is reopened again from the hard drive.

Norm

[captainslarty]

Hi Norm
An interesting theory, but one that I believe is totally incorrect.

The ram will either work, or will not, there are some situations where thermal issues or overclocking etc may cause problems over time, however, this would not be so selective as to alter things in such a way, it would simply lead to a bsod or total crash / corruption.

What is being described by Charlie sounds very much like 'memory leak' - which is software related, not hardware - and usually caused by a single program, but can be caused by multiple programs. One program 'leaking' can also cause issues with other programs that behave correctly although the OS should protect the individual APPS and odes well at this.

What basically happens is that a software (APP) program does not behave correctly - either due to programming errors, or OS errors in the API it calls - most likely is the first -
For example, when memory is used, it should be released after the program has finished with it - not just at the end of the program, but also during the operation of the program.
The normal way to test for this is to look at the memory usage over a period of time for that application. Usually, in the case of a classic memory leak, the allocation grows to a point that the program becomes unstable - in simplistic terms.

The other situation that can (and I think DOES) occur with the IDE, is that certain things are not working correctly in the area of memory housekeeping - and - indeed variable housekeeping.

I certainly have issues with exception errors still within the IDE which then cause instability or crash - especially if the APP is open a long time (days).. Some could be down to the compiler to IDE interaction, some down to one OR the other.
They are very rare, and not readily reproducable. THIS ONLY EFFECTS PDS AND THE IDE -
In my case, the main issue seems to occur with mutliple code windows open and using find - replace - and copy and paste between code windows.
Heavy use of this can and does often cause wierd and wonderful results including crash and exception errors.

The BIG problem is how to objectively prove this - it happens so infrequently, is not readily reproducable, so no real 'sample' code or usage pattern can be submitted to the developers to actually assist them in tracking it down.

I do support Charlie in the fact tht with the IDE open for a few days continuosly, there can and are issues. HOW to track these down ? - darn near impossible.
Hence, lack of useful reporting to the developers. There was a definite issue with exception errors in one of the previous Beta that les corrected (or possibly Les and Dave B - not sure) -
I still suspect some kind of interaction with find replace and copy paste over time. BUT, that is SUBJECTIVE, not unfortunately Objective.

Joe

[normnet]

As I understand it a "memory leak" occurs when a program is closed and doesn't free up the all of the ram it was using for use with other programs.

I do support Charlie in the fact that with the IDE open for a few days continuously, there can and are issues. HOW to track these down ? - darn near impossible.

An open program does reside in ram and if while the IDE is open over a few days an issue occurs, certainly one possibility is the program in ram is corrupted.


Norm

[captainslarty]

As I understand it a "memory leak" occurs when a program is closed and doesn't free up the all of the ram it was using for use with other programs.


An open program does reside in ram and if while the IDE is open over a few days an issue occurs, certainly one possibility is the program in ram is corrupted.


Norm

Hi Norm.
No, a memory leak is as said, a leak - a gradual accumulation of incorrect housekeeping either by the APP or the OS.
It occurs during the running of the program as is hence acccumulative.

Memory not being cleared at the close of an APP is not a leak, just a fault.

I do not believe for one minute that the actual RAM is being currupted due to hardware issues, a program open for a few days or more, that then tends to have issues, is virtually 99.99999999% to be an issue with the APP that is corrupting RAM. (NOT hardware!)
IF there was a hardware issue, it would be totally unpredicatable in ANY APP or OS function as the RAM is allocated dynamically - for the APP and paging.
Joe

[normnet]

Hi Norm.
No, a memory leak is as said, a leak - a gradual accumulation of incorrect housekeeping either by the APP or the OS.
It occurs during the running of the program as is hence acccumulative.

Memory not being cleared at the close of an APP is not a leak, just a fault.
Joe

From Wikipedia:
A memory leak, in computer science (or leakage, in this context), occurs when a computer program consumes memory but is unable to release it back to the operating system.

My understanding is a memory leak can occur during or on close as both fail to release it back to the operation system.

Norm

[captainslarty]

My understanding is a memory leak can occur during or on close as both fail to release it back to the operation system.

Norm

Hi Norm

From Wikipedia:
A memory leak, in computer science (or leakage, in this context), occurs when a computer program consumes memory but is unable to release it back to the operating system.

SHOULD READ

From Wikipedia:
A memory leak, in computer science (or leakage, in this context), occurs when a computer program consumes memory but does not, or is unable, to release it back to the operating system.

A memory will not 'occur' on program close, it has already occurred prior to program close. (The one caveat being on certain badly managed OS's. or during IPC shared access and badly managed OS)
It is an accumulative thing and process whilst the program is running -
I found your referenced wiki article, best read it all.
IF the above is occurring (on closure of the program) (which is not the 'cause' of the issue in a program becoming unstable after running continuously) - it would indicate, or tend to, an OS issue or failure to follow programming practice.

Again, read the whole wiki you quote from, it is generally informative.
99.99999% of the time on a modern OS it is an application issue. And certainly nothing to do with Ram 'getting older' to be so specific a result.
Joe

[normnet]

A memory will not 'occur' on program close, it has already occurred prior to program close.

Minor differences between opinions but their is some memory in use at the time of app close which could also fail to be released back to the OS.


All I know is on an ancient W98 PC a program will reopen with the current data if saved and closed a short while after data input however if the program isn't saved and closed for some time on the following reopen the last data input is gone.
The newest unsaved data input could have only existed in memory during the hours before save and app close leading to the conclusion that the RAM failed.
The program works fine on other PC's.

The boot up on my PC can include a ram test which would indicate RAM can fail.
I am talking about a very ancient PC.

Norm

[normnet]

I'm tempted to write a windows program which would load a very large array to utilize a good share of RAM and load the array with all binary 1's.
Then wait a few days and on button click test if the data has been retained as all 1's.

PC's require a reboot after a period of time or they become buggy which also may indicate RAM isn't always meant for holding data long term.

Norm