[4.62] Reaper hangs when loading a project with a huge number of tracks (FIXED)

[karoldvl]

Regarding my earlier experiences with huge orchestral templates in Reaper: http://forum.cockos.com/showthread.php?t=135046, I was able to reproduce the last issue I mentioned on a separate system (Windows 8.1) with a pristine clean portable installation of Reaper 4.62 64-bit (default settings).

Problem:
It seems that saving a project with a huge number of (empty) tracks makes it impossible to load it again (1000 works just fine, a test with 1250 fails).

Steps to reproduce:
1. Create a new empty project
2. Insert > Multiple tracks... > 1500 tracks
3. Save the project
4. Close the project
5. Try reopening the saved file - Reaper will become unresponsive when loading the project (massive to moderate CPU usage in the Task Manager).

Could anyone confirm this behaviour? Any way to debug it more thoroughly? It's not a crash, so I can't really find anything relevant here.

[DarkStar]

Here (Windows 7 64-bit, Reaper 32-bit):

• A project with 1050 empty tracks saves and opens OK, total CPU 13-19%, RT CPU 5.6%, using 4 of 8 cores, RAM 134 MB, free memory > 6 GB
• A project with 1051 empty tracks saves OK, total CPU 27-30%, RT CPU 7.6%, using 5 of 8 cores (> 90% of one of them), RAM 166 MB, free memory > 6 GB but does not load.

I reloaded the 1050-track project and added one more track:


WAG (wild-assed guess): could it be that on loading Reaper is only allocated 4 cores, but for that 1051-track project needs 5?

[karoldvl]

Thanks. Good to know it's not an idiosyncrasy of my setup(s).

I think it has something to do with the drawing loop. I have one project where saving with most tracks (north of 1000) collapsed into their respective folders will work fine. But saving the same project with all tracks expanded/uncollapsed will render it unloadable. Weird.

[Dstruct]

Confirmed (1500 tracks, Win8.1 64bit, REAPER 4.62 64bit)

FIXED (5.17pre1)