I'm using very similar options for packaging. python $EMSCRIPTEN/tools/file_packager.py audio.data --use-preload-cache --js-output=audio.js --preload ../assets/audio@audio
I'm using Firefox stable v32 and Chrome v37. As you can see, I'm using --use-preload-cache. I see a strange issue in Firefox with indexedDB. App fails to cache data and falls back to download the data everytime. This doesn't happen in Chrome though. TypeError: indexedDB is undefined Stack trace: openDatabase@https://emtest.parseapp.com/data.js:123:15 runWithFS@https://emtest.parseapp.com/data.js:249:1 @https://emtest.parseapp.com/data.js:255:5 @https://emtest.parseapp.com/data.js:9:2 data.js:221 "falling back to default preload behavior" data.js:222 On Wednesday, September 24, 2014 2:03:35 AM UTC-7, asnapper wrote: > > On Wednesday, September 24, 2014 5:10:29 AM UTC+2, Rayudu wrote: >> >> Crashes on Chrome and firefox shows the unresponsive script popup. >> Can you point me to some samples for compiling/compressing/decompressing >> data using gzip with my app? >> > > what options did you use for the file-packager? with firefox you can > easily several hundreds of MB alongside your emscripten application, > without getting any unresponsive script warning (tested in ff nightlies > 32-35 with data files up to 700MB). With chrome i didn't have any success > with anything above 50MB. > > here's how i package my filesystem: > python file_packager.py \ > data.dat \ > --use-preload-cache \ > --no-heap-copy \ > --preload `\ > find * -type f -name '*.cache' -exec echo {}@/cache/{} \;;\ > `\ > > data.js > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
