{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 ▲ chillily 的问题《Xlib screenshot call》','https://www.manongdao.com/q-666042.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
After seeing the question How to take screenshot (high fps) in Linux (programming) the discussion in the comments has exposed that even thought the problem of rapidly capturing the screenshots is well described. We couldn't actually find the description of the logic behind.
This question was created with intention of resolving the information regarding memory handling of the XLib screen capture
Does xlib screen capture copy the memory from kernel space into user space, or is it creating the intermediate buffer to store the data read from frame buffer?