Issues with pano view on the Chrome in OS x

crazyxoma · August 24, 2016 at 10:29 AM

Hello... Have the problem:
1. I have a planet view in the beginig
2. Have this code for animation on startup^

Code

tween(view.fov, <?= $curScene->fov ?>, 12,easeOutInCubic);tween(view.vlookat, <?= $curScene->vlookat ?>, 12,easeOutInCubic);
tween(view.hlookat, <?= $curScene->hlookat ?>, 12,easeOutInCubic);
delayedcall(6,tween(view.fisheye, "0.0", 6,easeOutInCubic));

3. Have the problem with tiles position during animation:

(this video from http://www.browserstack.com emulator, but real PC have the same trubble).

This trubble seen on Chrome browser v. 51,52 on Mac ... Probably - and lower...

What does it mean? How to fix it? My head is about to explode(((

klaus.krpano · August 24, 2016 at 6:54 PM

Hi,

the bug is not in krpano, the bug is in Chrome OSX (as it seems since Chrome 51)!

Additionally for me the bug is almost impossible to reproduce, it happens only once of 100 tries when on my Mac (and always only in external examples and never in my own ones) and so it's very difficult to find a potential reason and some hack or workaround to avoid that...

But as said the bug is in Chrome - Google is the blameworthy and the best for the moment would be reporting the bug/crash to Chrome!

Best regards,
Klaus

klaus.krpano · August 24, 2016 at 10:33 PM

Hi,

btw - please try Chrome 54 - currently available as 'Chrome Canary':
https://www.google.de/chrome/browser/canary.html

For me it seems that Chrome bug is already fixed there...

Best regards,
Klaus

crazyxoma · August 26, 2016 at 8:06 AM

Hello again...

The customer installed the latest version on the real Mac... The error does not appear yet (2 days). The client continue testing.

I'll let you know about the results =)

indexofrefraction · August 26, 2016 at 10:55 AM

for me it is an issue with the actual stable v52

the beta channel seems to be v53 but there i cant even start my tour:
"Adobe Flashplayer or HTML5 Browser with WebGL or CSS3D support required!"

also canary v54 shows the same error.

they have a lot of builds, but no release notes,
not even the version number is visible. thanks for that google.
https://www.chromium.org/getting-involved/dev-channel

ps. i tested only macos

klaus.krpano · August 26, 2016 at 11:33 AM

Quote from indexofrefraction

the beta channel seems to be v53 but there i cant even start my tour:
"Adobe Flashplayer or HTML5 Browser with WebGL or CSS3D support required!"
also canary v54 shows the same error.

That strongly suggests that your GPU drivers are the problem and are blacklisted therefore in the newer Chrome versions...

So the problem is mainly between Google and Apple, maybe a bug in Apple drivers and Goolge don't want to workaround it and simply blocks it...

Please note that such core system/browser bugs are nothing I could fix!
The best would be reporting the problem at Chrome.

Just for interest - what Mac system, what OSX version, what GPU?

And btw - could you please test using 'html5=always+css3d' in Chrome 53 and 54 and your system?
It would be interesting if at least CSS3D would work on such system...

Best regards,
Klaus

indexofrefraction · August 27, 2016 at 1:27 AM

hm.. that's weird...

i use a simple (mid 2011) macbook air with 10.10.5
so no special gpu, just what's built in

i have just one simple problem with v52:
i cant tween hlookat|vlookat.
everything else runs fine (on webgl)
ofc thats a problem depending on what you do.

on v53/v54 nothing works
forcing css3d doesnt help, it is blocked, too.
i didnt check on my mac pro... will do next week.

klaus.krpano · August 27, 2016 at 8:16 AM

Hi,

Quote from indexofrefraction

i use a simple (mid 2011) macbook air with 10.10.5
so no special gpu, just what's built in

Sorry, but that's too unspecific for looking up details about the problem...

Either check the OSX 'system report' for the GPU info - e.g. here:

or open the

Code

chrome://gpu/

url in Chrome,

and look for the 'vendor id' and 'device_id' numbers.

These information could be used to look in the source code of Chrome here for the reason of the GPU blocking/blacklisting:
https://cs.chromium.org/chromium/src/g…ng_list_json.cc
https://cs.chromium.org/chromium/src/g…ug_list_json.cc

Quote from indexofrefraction

i have just one simple problem with v52:
i cant tween hlookat|vlookat.

That's not the reason/source of the problem.

Best regards,
Klaus

indexofrefraction · August 27, 2016 at 9:32 AM

ok, i have a MacBookAir 4.2

VENDOR = 0x8086, DEVICE= 0x0116 *ACTIVE*
REVISION = 0x009 (from system report)

but i couldnt find the device id 0x0116 in the sources ... you?

on monday i will test how my mac pro in the office behaves...

klaus.krpano · August 27, 2016 at 7:38 PM

Hi,

yes, that can't be missed!

See here (line 1064):
https://cs.chromium.org/chromium/src/g…_json.cc?l=1064

And look at its description:
"Intel HD 3000 driver crashes frequently on Mac"

And because the Macbook Air Mid 2011 has an Intel HD 3000 GPU this make sense.
By further googling a bit about that there are a lot of results regarding a buggy GPU driver (not just Chrome related).

See here the discussion from the Chrome developers about that bug:
https://groups.google.com/a/chromium.org…ews/I6dL_9IAwiE

An interesting comment there:

Quote

The crashes on these GPUs were happening before GPU rasterization was turned on.
The HD 3000 in particular is really old, and has been problematic. For these
reasons I think it's OK to blacklist all GPU functionality on it, including
WebGL. Users can manually specify --ignore-gpu-blacklist if they want to try
content on it.

So your device is too old for Google...
And for Apple probably too because they don't care about providing a stable GPU driver...

Best regards,
Klaus

indexofrefraction · August 27, 2016 at 8:15 PM

hey, my air is my baby!!!!

and it's a bit nonsense with these gpu crashes...
i never experienced something, at least not that i was aware of it.

btw, if i start chrome v53 on the terminal with --ignore-gpu-blacklist
tweening hlookat|vlookat works totally fine again!

so.. problem solved, but now v53 blacklists my development device.
pfff...

hey but thanks klaus for giving these insights,
i wouldnt have found that myself!

EDIT:
tried on a mac pro: v53 works totally fine there.

klaus.krpano · September 1, 2016 at 11:50 AM

See also that post (about a bug in Chrome 52):
my pano website went nuts - jumping tiles.

Participate now!