Skip to content
This repository has been archived by the owner on Jun 28, 2019. It is now read-only.

Export full collection to csv #50

Closed
kwancho opened this issue Jul 7, 2015 · 8 comments
Closed

Export full collection to csv #50

kwancho opened this issue Jul 7, 2015 · 8 comments

Comments

@kwancho
Copy link

kwancho commented Jul 7, 2015

I have a pretty large collection, and when I click on the export to CSV, I get the "Fetching Favorites data... Please wait. If your Favorites is large this can take a while" popup, but then it goes away after about 10 seconds with no further actions.

Console error:
screen shot 2015-07-07 at 9 29 24 am

@matt-h
Copy link
Owner

matt-h commented Jul 7, 2015

Thanks for the report. The popup does disappear after about 10 seconds even if it isn't done (maybe I should add more if it is extra large).

That console error is unrelated to the export, so that shouldn't be the issue.

If you go to the Network tab in the Developer Tools it should be making multiple calls to "getTracksInCollection". If those continue without error then it is still building the CSV.

@kwancho
Copy link
Author

kwancho commented Jul 7, 2015

Ah, cool. It is still making those calls. Guess I'm just impatient!

On Tue, Jul 7, 2015 at 10:08 AM, Matt notifications@github.com wrote:

Thanks for the report. The popup does disappear after about 10 seconds
even if it isn't done (maybe I should add more if it is extra large).

That console error is unrelated to the export, so that shouldn't be the
issue.

If you go to the Network tab in the Developer Tools it should be making
multiple calls to "getTracksInCollection". If those continue without error
then it is still building the CSV.


Reply to this email directly or view it on GitHub
#50 (comment)
.

@matt-h
Copy link
Owner

matt-h commented Jul 7, 2015

You must have a large collection then. I'm curious how many tracks it ends up with and if it completes successfully.
The largest I've tested with so far is around 5000 tracks.

@kwancho
Copy link
Author

kwancho commented Jul 7, 2015

I let it run three times, and each time Chrome crashes out before it finishes

screen shot 2015-07-07 at 10 27 38 am

@matt-h
Copy link
Owner

matt-h commented Jul 7, 2015

That is a lot of tracks in your library, that is 20000 tracks worth of requests on the screen there.

Chrome is running out of memory and crashing before it can get everthing.

@matt-h matt-h closed this as completed in 83d8967 Jul 7, 2015
@matt-h
Copy link
Owner

matt-h commented Jul 7, 2015

I just uploaded version 2.8.5 which might fix this issue by breaking the download into multiple CSV files with 15000 tracks in each. When it is available to you please update to the new version and see if that fixes Chrome crashing on you.

@kwancho
Copy link
Author

kwancho commented Jul 7, 2015

So, it finishes collection and collection(1), which are each exactly 15,000
songs (up to T for me), but then for the third, the getTracks starts taking
~130ms instead of 6-8s and it doesn't end up completing. So close! Thanks
for the updates so far....

[image: Inline image 1]

On Tue, Jul 7, 2015 at 11:27 AM, Matt notifications@github.com wrote:

I just uploaded version 2.8.5 which might fix this issue by breaking the
download into multiple CSV files with 15000 tracks in each. When it is
available to you please update to the new version and see if that fixes
Chrome crashing on you.


Reply to this email directly or view it on GitHub
#50 (comment)
.

@kwancho
Copy link
Author

kwancho commented Jul 7, 2015

screen shot 2015-07-07 at 3 22 53 pm

matt-h added a commit that referenced this issue Nov 17, 2015
Also add start input to begin download at a certain number
Fixes #66
Fixes #50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants