Issue metadata
Sign in to add a comment
|
[Chrome]: Regression in March: Not able to render correctly for some 3D models on some user's latest Chrome browsers from Tinkercad
Reported by
helenlil...@gmail.com,
Mar 24 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Example URL: https://www.tinkercad.com Steps to reproduce the problem: I don't have reproducible steps as I am not able to reproduce this issue by myself. But we got about 5 reports from our users who have the issue in their Chrome. 1. They are creating the models in Tinkercad editor 2. Select one object and set it as a hole Actual result: 1. The workplane is disappeared and the hole is rendered wrongly. 2. Delete the hole, then everything is back to work. Notes: 3. IE/Firefox works well, they have no such problem for the same user in the same machines. 4. Users uninstall and install Chrome again, and reset the Chrome settings, still see the problem. 5. Users tried the same thing in Chrome Canary, few of them reported the issue is gone, and few of them reported the issue still exists. 6. Users reported this issue just this month since about Mar 11, 2016. But it worked well for those users in the past. What is the expected behavior? There should be no render issue for the objects in Tinkercad Editor. 3-Correct.jpg is the expected render result for the hole in Tinkercad. What went wrong? 1-wrong.png and 2-wrong.png, you could see the render result for hole is incorrect and the workplane about our editor is disappeared. Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? Yes We got the user reports about this issue since about Mar 11 Does this work in other browsers? Yes Chrome version: 49.0.2623.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 21.0 r0 IE/Firefox works well, they have no such problem for the same user in the same machines.
,
Mar 28 2016
We got the updated feedback from our users, they are still meet the issue in Canary, and now more and more users are reporting the issue to us on Chrome. While other browsers, e.g. IE, Safari, Firefox has no such issues. Anybody could help to have a check? Is it a known issue in Chrome? Thanks a lot. Regards, Helen
,
Mar 31 2016
If user run Chrome with --enable-native-gpu-memory-buffers, then everything is well. Do you know why the native gpu memory buffers is disabled for their Chrome? While my Chrome has no such issue.
,
May 2 2016
Issue looks similar to the bug 593725 .Hence merging this into 593725. Please feel free to undupe if not the case. Thanks, |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by helenlil...@gmail.com
, Mar 24 2016