diff --git a/README.md b/README.md
index be5077093..d148d0aea 100644
--- a/README.md
+++ b/README.md
@@ -60,6 +60,15 @@ Most of the time.
 
 If you compare HashMap, ConcurrentHashMap and Chronicle Map, most of the maps in your system are likely to be HashMap.  This is because HashMap is lightweight and synchronized HashMap works well for lightly contended use cases.  By contention I mean, how many threads on average are trying to use a Map.  One reason you can't have many contended resources, is that you only have so many CPUs and they can only be accessing so many resources at once (ideally no more than one or two per thread at a time)
 
+
+####  Known Issues
+
+Chronicle map lets you assign a map larger than your available memory, This will however impact performance as Chronicle Map will have to page the segments to and from disk as data is written or read from the map. This feature works brilliantly on Linux but unfortunately its not supported on Windows, if you use more memory than is physically available you will experience the following error :
+
+
+
+
+
 ####  When to use ConcurrentHashMap
 Some of the time.