Last Comment Bug 1332932 - No graphics shown in some of the canvas demo website.
: No graphics shown in some of the canvas demo website.
Status: NEW
Product: Core
Classification: Components
Component: Graphics (show other bugs)
: 52 Branch
: x86_64 Windows 10
P3 normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Milan Sreckovic [:milan]
Depends on:
  Show dependency treegraph
Reported: 2017-01-22 10:05 PST by Roshan Dawande
Modified: 2017-02-16 09:17 PST (History)
6 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: yes

screenshot1.jpg (75.33 KB, image/jpeg)
2017-01-23 22:24 PST, Roshan Dawande
no flags Details
Page-Shot-2017-1-31 Troubleshooting Information.png (214.88 KB, image/png)
2017-01-31 08:05 PST, Roshan Dawande
no flags Details
mozregression for windows Instruction.txt (801 bytes, text/plain)
2017-02-02 15:07 PST, Abe - QA (:Abe_LV)
no flags Details
mozregression.JPG (86.50 KB, image/jpeg)
2017-02-03 03:02 PST, Roshan Dawande
no flags Details
testcase.png (90.86 KB, image/png)
2017-02-03 08:59 PST, fahimazulfath.a
no flags Details

Description User image Roshan Dawande 2017-01-22 10:05:39 PST
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce:

Step 1- Launch Firefox.	
Step 2-Goto	
Step 3- Click on Blob's demos
            Click on MSX Emulator
            Click on 3D on 2D Canvas

Actual results:

No Graphics displayed.

Expected results:

some graphics should be displayed.
Comment 1 User image Loic 2017-01-22 23:53:06 PST
Can you attch screenshot for the link (3D on 2D Canvas)?
Comment 2 User image Roshan Dawande 2017-01-23 22:24:20 PST
Created attachment 8829754 [details]
Comment 3 User image Roshan Dawande 2017-01-23 22:38:47 PST
No graphics are shown in any of the case.
And in demo3, When i click "opera 3D or Gecko 3D" "This browser does not support any 3D canvas" message shows.
Comment 4 User image Abe - QA (:Abe_LV) 2017-01-25 10:19:45 PST
Hi Roshan,

I can see graphics using the link provided in comment 1. Could you please attach your "about:support" information? Thanks

Version 	54.0a1
Build ID 	20170124030205
Update Channel 	nightly
User Agent 	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0
Comment 5 User image Roshan Dawande 2017-01-31 08:05:33 PST
Created attachment 8832075 [details]
Page-Shot-2017-1-31 Troubleshooting Information.png
Comment 6 User image Abe - QA (:Abe_LV) 2017-02-02 15:07:47 PST
Created attachment 8833098 [details]
mozregression for windows Instruction.txt


I have added the extensions on aurora 52.0a1 based on the information provided in comment 5. I have with windows 10 64bits with NVIDIA GeForce GTX 745 graphics, unlike yours (intel HD).  So I could not manage to reproduce it.

Could you provide a regression range using the mozregression tool if it is a regression issue? 
I have attached installation and usage information about the tool.

Comment 7 User image Abe - QA (:Abe_LV) 2017-02-02 15:39:23 PST
Tested on latest nightly and aurora 52.0a2
Version 	52.0a2
Build ID 	20170122004006
Update Channel 	aurora
User Agent 	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 8 User image Roshan Dawande 2017-02-03 03:02:09 PST
Created attachment 8833262 [details]

I was able to reproduce this issue in Firefox Nightly also.
I didn't understood the steps to produce range from mozregression, Still i have tried.
Please check.
Comment 9 User image Loic 2017-02-03 05:19:57 PST
Mozregression failed because you entered 2016-12-10 was a good build for left boundary then you replied it was a bad build when the tool checked this build.

If 2016-12-10 is bad, just enlarge to older builds, like --good=51 or 50 (if you're sure FF50/51 are working fine).
Comment 10 User image fahimazulfath.a 2017-02-03 08:59:56 PST
Created attachment 8833342 [details]
Comment 11 User image fahimazulfath.a 2017-02-03 09:01:23 PST
BROWSER : Firefox Beta 51.0
Comment 12 User image Roshan Dawande 2017-02-15 23:49:21 PST
Not able to understand mozregression. Please provide a indepth description of the steps involved.
Comment 13 User image Loic 2017-02-16 03:57:59 PST
(In reply to Roshan Dawande from comment #12)
> Not able to understand mozregression. Please provide a indepth description
> of the steps involved.

When you run mozregression, you need to enter a valid interval for nightly builds, e.g. [good-bad] or more simply [good[.

In your case the build you thought good (2016-12-10) was in fact bad, so mozregression aborted.
Just reduce the date for good build, like good=51 or 50 (mozreg accepts release number), and try again. You don't need to specify a bad build, just "mozregression --good=XXX".
Comment 14 User image Abe - QA (:Abe_LV) 2017-02-16 09:15:52 PST
Could you try "mozregression --good=XX --bits=32" where xx is a known good build? Example, if 51 is a good build, then run "mozregression --good=51 --bits=32".

Note You need to log in before you can comment on or make changes to this bug.