ImageMaterialProperty not working on Chrome (Windows)

I'm on Win 7, Chrome Version 50.0.2661.94 m (64-bit)

In sandcastle, I can create image materials in firefox, but not on my chrome:

The sandcastle code is:

var viewer = new Cesium.Viewer('cesiumContainer');

var url ="../images/Cesium_Logo_overlay.png"

var redRectangle = viewer.entities.add({
    name : 'Red translucent rectangle with outline',
    rectangle : {
        coordinates : Cesium.Rectangle.fromDegrees(-110.0, 20.0, -80.0, 25.0),
        material : new Cesium.ImageMaterialProperty({image:url}),
        outline : true,
        outlineColor : Cesium.Color.RED


Looks great in firefox, nothing shows up in Chrome.

Is this a problem with my machine?


Thanks for providing a code sample! This sample ran fine for me in Chrome.

What version of Cesium are you using?

Have you tried clearing your cache or running in incognito mode? Sometimes cache can cause weird side effects in chrome if you are switching between versions of Cesium.



Thanks for replying Hannah,

Well, I’m running this on Sandcastle, which I assume uses the latest, though we use 1.18 in general development.

The only interesting thing I found after clearing my cache and running the code in incognito a few more times is that sometimes I saw the image material flash correctly for a split second before disappearing, but not always.

Also, when I zoom in to where the image should be, it struggles to render the globe and usually the Earth disappears until I zoom out again, so it seems to acknowledge ‘something’ is supposed to be there.

My machine has

Chrome 50.0.2661.94 m (64-bit)

AMD Radeon™ HD 8490, driver: 13.351.1007.1006

My co-worker has the same problem, so it’s not unique to my machine per se, but IT probably set us up with the same video cards. (which I will see if there are updates for). This is not the only thing that started being an issue with Chrome early this year…I’ve seen other shapes fail to show up, and I’ve commented on the picking bug.

I’ve created a GitHub issue here:
It might be an AMD specific bug, which is why I couldn’t reproduce it (I have an nvidia card)

We’ve noticed a few other weird bugs in Chrome 50, did this issue only start happening when you updated chrome?

The only other thing I would recommend is try updating your video card driver if it’s not already up to date.

Thanks for reporting this!


Thanks Hannah.

I swear I saw no Cesium issues until earlier this year, maybe upon Chrome 48 or 49’s release. That’s when I started to notice things like picking stopped working and sometimes my entities would not appear, especially if added right after the viewer’s initialization, but I haven’t tested these issues in depth because Firefox works. But I only started experimenting with ImageMaterialProperty this week.

Great, thanks for the info. It looks like other people have seen this too, so we’ll try to take a look into it soon.