Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It's possible a promise in unzipCUB3ds.js gets rejected without logging #90

Open
strycore opened this issue Jan 14, 2015 · 14 comments
Open

Comments

@strycore
Copy link

The README estimates the extraction time to 5 minutes on "normal hardware"but I've launched the extraction procedure more than an hour ago and it's still working at it!

My guess is that the operation takes around 5 minutes per exported tile (I have exported something like 25 tiles), the docs should probably mention that.

@DavidBruant
Copy link
Contributor

True. One my machine, it's about one minute per exported tile.
What hardware/OS do you have?

(I'll change the doc right away)

@strycore
Copy link
Author

I'm running this on a Core 2 Quad @ 2.66Ghz with Ubuntu 14.04 x64.
The operation is still running btw and I don't see any generated files, either in /tmp/tmp-15284e5gphsg or in front/data (both folder empty, except for a .gitkeep in data)

@DavidBruant
Copy link
Contributor

Something went wrong. It's possible a promise got rejected and we don't log its error.
I'll give it another try.

@DavidBruant DavidBruant changed the title README indicates wrong time estimate to extract 3D data It's possible a promise in unzipCUB3ds.js gets rejected without logging Jan 14, 2015
@DavidBruant
Copy link
Contributor

We're finishing a major refactoring, so it's possible things don't all go well, sorry about that.
Repurposing the issue.

@DavidBruant DavidBruant reopened this Jan 14, 2015
@strycore
Copy link
Author

aaah, much better :D The extraction is quite fast (2~10 seconds/tile)

@DavidBruant
Copy link
Contributor

what is much better?
Does it work because you did git pull?

@strycore
Copy link
Author

No, I just stopped the process (which had been eating 100% of a core doing nothing) and relaunched it without changing anything. The extraction process worked as expected.

@DavidBruant
Copy link
Contributor

Ok. Closing then...

@strycore
Copy link
Author

Probably not worth opening a new issue: there's a missing 'run' between npm and 'start-dev'.
Got the project to run but it's completely unusable on this machine, will try again at home with a proper GPU.

@DavidBruant
Copy link
Contributor

Probably not worth opening a new issue: there's a missing 'run' between npm and 'start-dev'.

Fixed. Thanks :-)

@vallettea
Copy link
Contributor

I jsut stumbled upon the same issue node unzipCUB...

@vallettea vallettea reopened this Jan 21, 2015
@vallettea
Copy link
Contributor

Related from @iOiurson (french):

Grosso modo, le problème n’apparaît que lors de l’unzip de gros fichiers .zip.
Je sais pas exactement le seuil, mais jusqu’à 110Mo zippé, ca marche, >250Mo, ca ne marche pas.

En fait, le pb est dans unzipInTmpDirectory. Je me rappelle on avait discuté de ça fin décembre parce que j’arrivais pas à unzip une tile avec textures.
Je pense que le problème est le même: le fichier est trop gros.

Du coup, l’évènement « finish » se lance, mais pas l’évènement « close », ou se trouve le def.resolve.
Quand le fichier est petit, finish trigger, puis close, donc on a pas de problème.
Quand le fichier est plus gros, donc, close ne trigger jamais.

Pour fixer les idées, sur bordeaux centre, il y a une cinquante de fichiers zip à extraire, mais seulement 40 se retrouvent dans le tmp.

@DavidBruant
Copy link
Contributor

Maybe duplicate of #76

@vallettea
Copy link
Contributor

indeed but let's close this one and see it fixes the other one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants