We currently have the premium version of Web2Cal, but we found out that it is causing a huge memory problem.
When we open a page with the web2cal calendar it causes to eat up a chunk of memory around 600MB, which will cause a crashes on several systems.
You can reproduce this on the following systems:
- iPad (IOS 4) (immediate crash);
- iPhone 4 (IOS 4) (immediate crash)
- Windows XP in combination with Safari 5 (immediate crash when not enough memory);
- Mac OS X 1.6 with Safari 5 (Takes a few refreshes to crash);
I am not sure what part of the library is causing this (in combination with some rare Safari bug),
but when I am looking at your compressed code I noticed you are using eval to load the entire library, can I ask, why???
You can reproduce this on your demo calenders on your own website asswel.
This issue is because of the obfuscator. Apparently, Safari\'s mysterious bug is unable to handle large lines of eval code. We are working on replacing ( Currenlty Testing ) the obfuscator. Should be out shortly. Will keep this thread posted.