![]() ![]() It appears that Sonar's memory manager has been much improved, and is now efficiently disposing allocated memory blocks when appropriate. In Sonar 8, this kind of thing doesn't happen. Of course, these kinds of bugs are non-reproducible, so there's no way you can report it, (though many would come to the forum and try.) Most of the time, inserting a new plugin went normally, but randomly, it would crash a project. I imagine this problem, combined with other inefficiencies, was causing a well-worked project to crash without apparent cause, for instance, the simple act of inserting a new plugin would caused a crash - it was a random thing. With a fragmented heap, programs can't allocate sufficient memory, even when the system reports there's plenty of free RAM available. ![]() Sonar 7 appeared to leave memory fragments around after the program no longer needed them, causing a problem called heap fragmentation. All software has its problems, but in this case, the odds are good that you'll pleased with the upgrade.įor example, when I left Sonar 7 running overnight, most of the time I'd find the program crashed in the morning - very strange considering no one was working at the time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |