New Traktor crashes when loading tracks multiple times quickly.

Over the years I've seen a lot of reports of Traktor crashing when a user loads a track. As a software engineer I appreciate how hard these are to fix because they're not reproduceable in repeatable manor. Recently I've had a few crashes when loading tracks into decks and into the Preview Player. One I can't reproduce consistently, I basically disconnected a network drive and Traktror crashed making me think that maybe Traktor has issues when disk I/O gets interrupted. The other issue I can reproduce and could also be disk I/O related.

I tested this on a fresh install of Traktor Beta 3.5.2 284 and I didn't import my collection or settings, unfortunately I don't have a second computer to test on. I do want to point out I have a rather fast computer 3.7ghz i7-8700K, 16gb RAM, Samsung 960 EVO 1TB M.2 SSD running Windows 10.

If you mash on the load button to load a track multiple times quickly Traktor crashes:



I've also tried just leaving Traktor and not clicking close and it eventually crashes.

I appreciate that you might be thinking "well stop hammering on the load button" but I believe this issue can happen under much lighter circumstances and by solving this problem it'll solve a lot of the issues other users are experiencing in similar situations. For example, I use the Preview Player and sometimes the track fails to load or loads slowly (another bug I can't yet reproduce but maybe related) this causes me to reload the track into the Preview Player thinking there's an issue with the controller, hitting the button just 3 or 4 times on a very rare occasion causes Traktor to crash.

Is Traktor running into a brief I/O issue (low I/O?) and it throws an uncaught exception and crashes?

Unfortunately there doesn't appear to be anything in the crash logs.

If someone else could let me know if they can also reproduce this error that'd be great, sometime you have to mash away for a while. Happy to do further tests to get to the bottom of this just let me know what needs doing, and apologies if it takes me a while to reply

 

Thank you for this detailed report.
We were able to reproduce the issue just by loading a track via the keyboard using Shift + Left Arrow key.
The issue is now filed as : TP-16559 and we'll have a look into it.