You are not logged in.

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

HansNyb

Professional

  • "HansNyb" started this thread

Posts: 936

Location: Denmark

Occupation: Photographer

  • Send private message

1

Saturday, March 28th 2015, 8:35am

Do you still use 1.17 PLEASE UPDATE

I have been doing museum tours since 2012.
My first tours uses png popups for text and therefore uses a lot of memory which sometimes crashes Safari.
My last tours uses HTML text with textfield and that has almost removed all crashes.

I also updated my older tours to 1.17 in december with multiresolution and that was no problem on my iPad 3 with IOS 6.1.3
Almost no crashes.
However on my iPad air with IOS 8 i got into problems all my older tours crash often already after the first pano.
I can se that there are a lot of comments with memory crashes for the Air if you search for iPad air crashes

However today I discovered that they are still with KRPano 1.17 so I tried updating to 1.18.2 and to my surprise it removed all crashes.

I still have the tour with 1.17 on this server http://virtualdenmark.dk/dnm/kina/

Here is the updated with 1.18.2 http://360-foto.dk/kinesisk-besog/

You may see that the 1.17 has a very slow way of opening each pano. It stays blurred for along time. This only happens on the Air. My old iPad 3 performs fine with the 1.17.

HansNyb

Professional

  • "HansNyb" started this thread

Posts: 936

Location: Denmark

Occupation: Photographer

  • Send private message

2

Saturday, March 28th 2015, 11:28am

Sorry I also got another problem but I solved that one.

This post has been edited 2 times, last edit by "HansNyb" (Mar 28th 2015, 11:48am)


3

Monday, March 30th 2015, 10:47am

Hi,

these crashes were related to a new bug that Apple introduced with iOS 7 / Safari 7.

With krpano 1.17.3 a workaround for this Apple bug was added:
http://krpano.com/news/#news1173
krpano 1.17 (Final Release)

Best regards,
Klaus