544607 - Add Shmem::IsWriteable/Shmem::IsReadable

Status: RESOLVED FIXED

(Core :: IPC, defect)

Description

[Joe Drew (not getting mail)]

Attachment: patch

We need a way to tell if a given shmem segment is readable and/or writeable, because otherwise we have no way of detecting whether we've sent a back buffer to a rendering process.

Comment 1

[Oleg Romashin (:romaxa)]

On my device when I'm running e10s fennec with user permissions, I have problem with rendering asyncXul content:
***********************
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMCanvasRenderingContext2D.asyncDrawXULElement]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://browser/content/TileManager.js :: render :: line 681"  data: no]
***********************


It is always failing in:
mBackBuffer.IsWritable() - always return PR_FALSE.


When I'm running the same stuff with root permissions, then it is rendering some tiles, but not all... 

I this we have some problems with shm segments creation... any ideas which parameter can limit this thing for user/root/system?

Comment 2

[Oleg Romashin (:romaxa)]

AllocShmem - fail in nsCanvasRenderingContext2D::CreateShmemSegments.

I did a bit more deep debugging, and it seems like 
mkstemp("/dev/shm/org.chromium.XXXXXX"); always return -1

Comment 3

[Doug Turner (:dougt)]

Oleg's problem is specific to the non-production device he is running on.

Comment 4

[Doug Turner (:dougt)]

http://hg.mozilla.org/mozilla-central/rev/52b381b8b00d