Closed
Bug 813296
Opened 12 years ago
Closed 12 years ago
Out of PMEM error when trying to call navigator.id.request() on b2g/latest, 2012-11-19
Categories
(Core Graveyard :: Identity, defect, P1)
Core Graveyard
Identity
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jedp, Unassigned)
References
Details
Attachments
(1 file)
4.26 KB,
text/plain
|
Details |
Testing Identity login on unagi_2012-11-19 (https://releases.mozilla.com/b2g/latest/) fails with "Out of PMEM errors" Preliminary steps: Preffed native identity on by pushing user.js into /data/local/ (as described in Bug 811528) To test, I visit this page in the browser on the phone: http://people.mozilla.com/~jparsons/demo.html Logcat shows that navigator.id.watch() is called successfully. When I click the login button, which is bound by jquery to navigator.id.request(), I get an explosion of errors like these: E/memalloc( 109): /dev/pmem: No more pmem available W/memalloc( 109): Falling back to ashmem D/memalloc( 109): ashmem: Allocated buffer base:0x4df00000 size:1413120 fd:100 D/memalloc( 483): ashmem: Mapped buffer base:0x44000000 size:1413120 fd:34 D/memalloc( 109): /dev/pmem: Allocated buffer base:0x4af00000 size:614400 offset:2990080 fd:112 D/memalloc( 109): /dev/pmem: Allocated buffer base:0x4af00000 size:81920 offset:8065024 fd:148 D/memalloc( 109): Out of PMEM. Dumping PMEM stats for debugging This error does *not* occur with today's cut of mozilla-central, which apparently works just fine. (tip of my m-c repo is @258292c9c929, dated Mon Nov 19 15:35:06 2012 +0000) In each case, I am using gaia master from nov 19, @b2eb3e62
Reporter | ||
Updated•12 years ago
|
blocking-basecamp: + → ?
Updated•12 years ago
|
Severity: enhancement → critical
Reporter | ||
Comment 1•12 years ago
|
||
Symptom: Page hangs and becomes unresponsive Logcat appears to show no more output other than PMEM messages.
Running out of pmem isn't a fatal or destructive problem. We just fall back on slower texturing. I suspect there's something else going on here.
Reporter | ||
Comment 3•12 years ago
|
||
(In reply to Chris Jones [:cjones] [:warhammer] from comment #2) > Running out of pmem isn't a fatal or destructive problem. We just fall back > on slower texturing. I suspect there's something else going on here. Thanks, Chris. I think you are right. With today's latest build, I can no longer reproduce the symptoms. I just tested with https://releases.mozilla.com/b2g/latest/unagi_2012-11-20.zip (it is now one day later) and while the "out of pmem" errors are still occurring, the persona logins are now working fine. I've tested: http://notoriousb2g.123done.org http://people.mozilla.org/~jparsons/demo.html If the pmem issue was a red herring, I can only hypothesize that some identity patch that was in m-c had not made the cut for latest. I'm inclined to close this as invalid, but I'll let Jason make the call. Jason, what do you want to do?
Reporter | ||
Updated•12 years ago
|
Flags: needinfo?(jsmith)
Comment 4•12 years ago
|
||
Works for me on 11/20 build.
Status: NEW → RESOLVED
blocking-basecamp: ? → ---
Closed: 12 years ago
Flags: needinfo?(jsmith)
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•