MarkerClusterer, MarkerClustererPlus: Markers sometimes not showing in Chrome

[GoogleCodeExporter]

Demo link or sample code:
http://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer/e
xamples/simple_example.html
http://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclustererpl
us/examples/simple_example.html

What steps will reproduce the problem?
1. Open one of previous links in Chrome (Win 7)
2. Click on the cluster 2 near Ottawa (it can be also the one near Nicaragua)

Expected result:
You should see two red markers.

Actual result:
Sometimes you see no markers until you make click, drag or mouseover on active 
map point.
If you see two red markers, refresh the page and repeat the steps once or twice 
and you should get the bug (missing red markers).

I can see this behaviour only in Chrome. Firefox, Opear and Firofox always show 
the markers.

Browser / Operating System:
[Chrome 32.0.1700.76 m / Win7]

Additional comments:
Wild guess: It could be some internal Chrome issue with rendering canvas 
elements.

*********************************************************
Tip: Star this issue (next to title) to receive notifications of status
changes against this issue, also used as a gauge for how many people are
interested in seeing it resolved.
*********************************************************

Original issue reported on code.google.com by jiri.koz...@gmail.com on 27 Jan 2014 at 10:13

[GoogleCodeExporter]

I have created similar bug report for Google Maps API, because I observed 
similar behaviour in official Google Maps example:
https://code.google.com/p/gmaps-api-issues/issues/detail?id=6293

Original comment by jiri.koz...@gmail.com on 27 Jan 2014 at 10:38

[GoogleCodeExporter]

I've tried this in all browsers on my machine (Win 7) using 32.0.1700.107 m, 
Firefox 24 and 27, and Internet Explorer 8, 9 and can't reproduce it.  I've 
refreshed about 20 - 30 times on each and have not seen the issue.

I would suggest it is an issue on your machine, but what it could be I have no 
idea really...sorry I couldn't be of more help!

Original comment by brett.mc...@gmail.com on 20 Feb 2014 at 2:02

• Changed state: NeedsMoreInfo

[GoogleCodeExporter]

Thank you for your reaction.

We observed this behaviour also on other computers with Chrome 32.0.1700.76 m.

Fortunately it seems it was problem of Chrome 32.0.1700.76 m, that is already 
fixed, because few versions later everything started to work.

Original comment by jiri.koz...@gmail.com on 20 Mar 2014 at 9:11

[GoogleCodeExporter]

Original comment by brett.mc...@gmail.com on 20 Mar 2014 at 2:05

• Changed state: Invalid