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.

1

Wednesday, September 21st 2016, 6:39pm

Safari Web Content quit unexpectedly! (pano video/soundinterface)

hello klaus,

i m relatively new to 360/pano videos...
but did a lot of tests today, and every some hour i got a

" Safari Web Content quit unexpectedly. "

- i m using one m4v file playing as pano video
- i use soundinterface playing two mp3s at the same time
- i use safari 10 release of 21.9.16 on 10.10.5

does anybody know if this is related to the mv4 file format?
or is it safari 10?
the multiple mp3s?
could there be other reasons?

best,
index

1.19pr7

This post has been edited 5 times, last edit by "indexofrefraction" (Sep 22nd 2016, 10:28am)


2

Thursday, September 22nd 2016, 6:38pm

Sounds very much like a Safari bug...

3

Thursday, September 22nd 2016, 10:18pm

i fear that, too... but am i the only one who reports this?
i could send u the bug report if u want...

This post has been edited 1 times, last edit by "indexofrefraction" (Sep 22nd 2016, 11:38pm)


4

Saturday, September 24th 2016, 6:27pm

i think it might have been one of my mp3 files i was playing

its 2h long and might have had some encoding error...

(it played in sound interface but i couldnt open it in my audio editor)

I will test this further...

5

Wednesday, November 9th 2016, 9:00pm

Same strange crashing behaviour here.
1.19-pr8

And the weird thing now:
Plays fine in one iPhone6S plus... and crashed the other - my iPhone6S plus... both running the newest (10.1.1) - but already happened in 10.0.x. And we do not see any difference in these phones... Both Safari.
The clip just worked fine in iOS 9.X

Does this makes sense at all?

Stefan

6

Monday, November 14th 2016, 4:16pm

Maybe one phone has still cached files from an old version...?