sorry I mean

" ldmicro closes with NO message in the middle of compilation (everything that haven´t been saved is erased for ever)"

thanks for your reply, it must be a pc problem then, but wich one?

I assume that you have removed it from your computer and reloaded it put the latest version and remove all the old versions and save them with the most modern version I use 2 LDMicro The version v5.4.1.1 and the French version that is for IC2.
you don't have to let Windon deactivate after a while with the program running and/or.

This made me sick and I removed the program since it conflicted with previous series and when you save or copy it, it doesn't find the right folder since you have them doubled or repeated (they remain crusty and you have to liquidate them.)

To Paulino:

Where Can i find the French version to use I2C?

is it from here? : https://github.com/joegil95/LdMicro32

Can you try this version?

the ldmicro from github is 32 or 64 bits?

https://github.com/LDmicro/LDmicro/releases/tag/5.4.1.1

I see, thank you very much for sharing your version

Yes, the performance issue in LDmicro, as described in the discussion threads, appears to be related to the software design, specifically with the ForgetFromGrid() function. Below are the key points explaining how this function contributes to the slowdowns and stability problems.

Description of ForgetFromGrid()

Function: ForgetFromGrid() is responsible for freeing elements from memory that are no longer needed in the graphical representation of the circuit (grid). This function is called each time an attempt is made to delete a contact or an element from the circuit.

Identified Problem: During testing, it was observed that when trying to delete an element that is no longer present in the DisplayMatrix array, the function enters a loop that can iterate up to 5,120,000 times. This happens because some elements have been previously removed and exist only in the undo history.

Consequences of the Design

Degraded Performance: As multiple insertions and deletions are performed, the performance of LDmicro significantly degrades. Operations that should be instantaneous become slow, affecting the user experience.

Unexpected Crashes: In another thread, it was reported that LDmicro closes unexpectedly, which may be related to memory management issues or unhandled errors arising during the execution of functions like ForgetFromGrid().

Undo History: The fact that the problem intensifies when reaching a limit in the undo history (32 items) suggests that the management of this functionality also needs to be reviewed and optimized.

Recommendations to Address the Problem

Optimization of ForgetFromGrid(): Review and optimize the code of this function to avoid unnecessary loops. It might be helpful to implement a mechanism that checks whether the element to be deleted actually exists in the DisplayMatrix before attempting to free it.

Review Undo History Management: Consider implementing a system that better manages the undo history, perhaps by limiting the number of items or removing elements that are no longer relevant.

Stability Testing: Continue testing with alternative versions of LDmicro that have proven to be more stable, and consider user feedback to identify other problematic areas.

Conclusion

The software design of LDmicro, particularly regarding the ForgetFromGrid() function, seems to be a critical factor in the performance and stability issues that users are experiencing. Addressing these design problems would not only improve the efficiency of the program but also increase user satisfaction. If you have any further questions or need more information on this topic, I would be happy to help! Feel free to post this translation in the LDmicro forum! If you need any adjustments or additional information, just let me know.