Add Shmem::IsWriteable/Shmem::IsReadable

RESOLVED FIXED

Status

()

defect
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: joe, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Posted patch patchSplinter Review
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.
Blocks: 524180
Attachment #425581 - Attachment is patch: true
Attachment #425581 - Attachment mime type: application/octet-stream → text/plain
Attachment #425581 - Flags: review?(jones.chris.g)
Attachment #425581 - Attachment description: add isreadable → patch
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?
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
Attachment #425581 - Flags: review?(jones.chris.g) → review+
Oleg's problem is specific to the non-production device he is running on.
http://hg.mozilla.org/mozilla-central/rev/52b381b8b00d
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.