-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zoom Crash from Touch Input on Viewer Initialization #4177
Comments
Interesting. Not sure if this is the same issue but I can get a similar crash with un-panned mouse-zoom starting from the upper-left corner (0,0) as mentioned in your gist. Here are my reproduce steps:
The result is Cesium crashes the render loop with
Clearly the camera has moved into NaN territory. |
+1 |
+1 |
@emackey the issue for your use case is that //>>includeStart('debug', pragmas.debug);
if (isNaN(result.x) || isNaN(result.y) || isNaN(result.z)) {
debugger;
}
//>>includeEnd('debug'); I think this points to your issue and the original issue being the same thing, but I'm not sure what the fix is. Perhaps @bagnell has some thoughts. We really need to get #3605 into master, as it would have caught this way earlier. |
Seems to be the same as this: #4440 |
Yes, it does seem like it's likely the same issue. We were never able to reproduce it with a mouse before so it seemed to be touch specific. Thanks for providing us with all the details @smills2929! When we fix this, we'll just double check to make sure #4440 is fixed as well. |
Is someone able to look at this today at the bug bash? |
I'm looking at touch/pointer events in general today. |
After initializing a viewer, if any zoom touch events occur before a pan (rather difficult to gesture a zoom before a pan with touch, but doable), a render error occurs and causes the viewer to crash.
Here is a link to a Gist page with code that can be used to reproduce the error (a touch input device is needed, or some ability to emulate touch events):
https://gist.github.com/amc723/508009b296ca4783f7a55eb57e038ac6
The text was updated successfully, but these errors were encountered: