Bugzilla – Bug 1319
Windows: Excessive delays repeatedly opening/closing long projects (sometimes)
Last modified: 2018-08-20 11:45:30 UTC
I created a large project (four tracks, each with four hours of generated white noise). In a windows release build, with a 3.6 GHz CPU, I open and close repeatedly. Usually between the 7th and 11th opening (it varies), reopening becomes slow and freezes the program for several seconds. It remains slow after.
I separated this concern from 218, which is slowness on windows for some display updates after opening such large files. Testing with random debugger interrupts and more systematically with Process Monitor suggests both problems are the consequence of memory fragmentation after many excessive small allocations. Surprisingly, creation and destruction of many wxFileName objects appears to be the problem. There are several fixes that might help. Fewer help just the display update after opening, which is the topic of bug 218.
Bug #1339 "Jumbled window while opening long project" also relates to this
To distinguish this better from bug 1339 I changed title from "Excessive delays opening long projects on Windows (sometimes)" to "Excessive delays repeatedly opening/closing long projects on Windows (sometimes)". I'm not sure it's P2 except that it may be caused by the same problems as bug 218 (P2) but I added this issue to the release note for bug 218 because that is more convenient for users.
This problem is exacerbated by the fact that there is no progress indicator to indicate progression through the "open" process (as there is with the application of effects on such large projects - which serve to reassure the user that something is happening and progress is being made). Accordingly I would recommend that we add a Progress Bar to the "Open" process. Note that Import already has such a Progress BAr.
This looks to be a close cousin of long-standing P2 Bug #218 It may even be a duplicate
Testing on 2/2/2 W10 on my Laptop working with the 256 GB SSD with a 12 hour project opening and closing 12 times I see no slowdown similarly saving the 12 hour project to the onboard 1TB hard disk I also see no slowdowns with a cycle of a dozed opens/closes Opens done with a mixture of File > Open and File > Recent Files It seems to me that for a large data set - you need a powerful PC. I can recall no recent complaints about this on the Forum so I am going to close this as WORKSFORME
