Flushing background task when closing makes Traktor crash/freeze

I've encountered the "Flushing background tasks" crash several times, after preparing tracks in my preparation/play list. I've tried waiting a long time to let Traktor close down, but apparently the only way to shut down the program is to use the Task manager. This is VERY annoying as no backup of the cue points or added tracks is made, so I loose al my work.

Maybe I should close and restart Traktor everytime I made a couple of changes to my playlist, but this kills my workflow. Any one who knows why this error occurs and NI, please fix this "bug"?

 

as a workaround, you could rightclick on your colleection in the browser tree and click "save collection". That way you won't lost all the changes you made when Traktor crashes.

 

Yes very much so I had to keep on saving my collection everytime I add songs to my playlist.Terrible bug it mostly happens in 2.6.4

 

Good tip Arkuu, I'll give that a try. Apparently, I'm not the only one to "enjoy" these lovely crashes..grrrrrrrrrrrrrrrrrrrrrrrrrrrrrr

 

+1 Verry annoying. and it happens quite a lot.. It's also in 2.6.5

 

people still have this ?

 

I do, and I use the (almost) latest Traktor version 2.6.4 and my computer is a I7 with 8 Gig memory. Now, when I prepare my playlist, after doing 5 songs, I close Traktor and restart, just to be sure..

 

I don't think having an I7 or anything else has to do with that problem

 

I don't think so either, but I mentioned it to avoid people reacting with "Maybe your computer is to old..., slow..outdated...whatever"

 

my computer is old and i don't have this issue

 

Same thing started happening to me after my upgrade 2.6.4
Painful after you've spent an hour or so prepping all your tracks and losing everything.
Thanks for the tip on saving the collection before shutting down. Much appreciated

 

Once in a while when I get " the spinning beachball" when closing Traktor, I have found that unplugging the usb audio interface (S4 or DJM900 in my case) sometimes helps it close normally.

 

Thx for the tip Apford, will try that next time it happens.

 

Had another "Flushing background" crash after putting cue points in about 20 or so tracks. I waited a long time (+- 1 hour) to give Traktor the time to get the flushing done. I did notice some disk activity, but I'm not sure this had anything to do with Traktor itself.

After awhile, I used taskmanager (ctrl-alt-del) but instead of shutting down Traktor as I usually did, I signed off and then logged in again. I had locked all the tracks that I cued up, but the locks didn't show in my list. I presumed that all my work was lost...untill I loaded one of the tracks into a deck and I noticed that the cue points were present. Also, after loading the track, the lock appeared in the list. So all I had to do was load all the tracks one by one into a deck and all my cue points & locked status re-appeared. My work was saved..

The crash is still annoying, but my work is saved, so I can live with it (but still NI, please fix it)

PS no usb device/controller was connected, so there was nothing to unplug (see previous post)

 

I haven't had the issue lately and I don't know why...no upgrade, no nothing. I noticed it happened pretty regularly when recording a mix of an hour or so, but I've been doing so again and not having the issues.

Actually, scratch that, I upgraded to Scratch, so maybe that doesn't have the issue? I'm not sure if the last time it occurred if I was on 2.6.4 or TSP. I know it happened regularly on 2.6.4 though.

Best bet is to lock the files you've been editing and save your collection before trying to close Traktor, at least until the issue is resolved.

 

ppl with crashes pls contact NI support on this!

 

check out djtechtools Mr golden showed a way to do auto save

 

can you show us please how?

 

I know how to 'save collection' without shutting down traktor. But when I do quit traktor 2.6.6 it hangs.. With all due respect, please don't respond unless you have experienced it and have found a SOLUTION/WORKAROUND it just saves a lot of time that's all..

 

Same here. This happened to me on a PC, and to a friend on a Mac the day before. The crash doesn't even bother me, but how on earth could they still not have added an autosave feature? :angry:

Crashes happen. You can fix one bug, and another one will appear. You need autosave to protect your work from ANY bugs and errors.

Look at the irony of this! This forum post has just been "auto-saved". Can you believe it?
So NI rather auto-saves some stupid forum post than the Traktor collections of their users. I just don't understand it :S

Autosave, autosave, Traktor needs autosave for god's sake!