Closed
Bug 459851
Opened 16 years ago
Closed 16 years ago
windows mobile System.privateBytes and -memstats privateBytes always returns 0
Categories
(Tamarin Graveyard :: Virtual Machine, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
Future
People
(Reporter: dschaffe, Assigned: tierney)
Details
Attachments
(1 file, 1 obsolete file)
2.77 KB,
patch
|
treilly
:
review+
lhansen
:
superreview+
|
Details | Diff | Splinter Review |
In windows mobile the privateBytes in memstats and System.privateBytes is unimplemented and always returns 0.
linux is also unimplemented see bug 459038
testcase:
add to end of an existing test:
import avmplus.System;
print('private bytes: '+System.privateBytes);
in acceptance tests see test in:
as3/ShellClasses/toplevel.as
Flags: wanted-flashplayer10+
Flags: in-testsuite+
Flags: flashplayer-triage+
Flags: flashplayer-qrb?
Updated•16 years ago
|
Assignee: nobody → treilly
Status: NEW → ASSIGNED
Flags: flashplayer-qrb?
Priority: -- → P2
Target Milestone: --- → Future
Updated•16 years ago
|
Flags: flashplayer-qrb+
Assignee | ||
Updated•16 years ago
|
Assignee: treilly → tierney
Assignee | ||
Comment 1•16 years ago
|
||
Attachment #385390 -
Flags: review?(treilly)
Comment 2•16 years ago
|
||
Comment on attachment 385390 [details] [diff] [review]
Implement private bytes for winmo
I'm +1 this b/c its coming from the player where it work supposedly, I don't get it. Getting Lar's to suprev.
Attachment #385390 -
Flags: superreview?(lhansen)
Attachment #385390 -
Flags: review?(treilly)
Attachment #385390 -
Flags: review+
Comment 3•16 years ago
|
||
Comment on attachment 385390 [details] [diff] [review]
Implement private bytes for winmo
I want to see reasonably good documentation of the winmo mechanism, notably the meaning of addr and endAddr which both seem arbitrary without that info. (Notably the correctness of both.)
I also think that instead of ifdeffing the function to death you should have a function for non-WINCE and another one for WINCE. Attaching the doc'n to the WINCE function would be appropriate.
Attachment #385390 -
Flags: superreview?(lhansen) → superreview-
Assignee | ||
Comment 4•16 years ago
|
||
I looked into the addr/endAddr stuff and found this link from MS explaining the memory layout under CE:
http://msdn.microsoft.com/en-us/library/bb331824.aspx
So it looks like 0x10000 - 0x2000000 is the 32mb that makes up the "process slot" (figure 2 in the link). I believe GCHeap allocates memory out of the large memory area (0x42000000 - 0x80000000) to avoid the 32mb limit, so the 2nd half of the code tries to walk through those regions and account for the memory used.
However, according to the link this is how CE 5.0 and earlier works, so I'm not sure if any of this applies to CE 6.0, and I think we're mostly running on 6.0 now.
I'll have to ask rob about it, as he wrote this code, but he's out this week.
And I will change the ifdef madness too.
Assignee | ||
Comment 5•16 years ago
|
||
Added documentation to patch, broke WinMo version into its own ifdef'ed function instead of ifdefing the implementation.
Talked to rob, and it turns out that WinMo 6.0 is built on top of WinCE 5.0, so that is why we have to do all the funky memory walking.
Attachment #385390 -
Attachment is obsolete: true
Attachment #386976 -
Flags: superreview?(lhansen)
Attachment #386976 -
Flags: review?(treilly)
Updated•16 years ago
|
Attachment #386976 -
Flags: review?(treilly) → review+
Comment 6•16 years ago
|
||
Comment on attachment 386976 [details] [diff] [review]
Updated patch
Nice.
Attachment #386976 -
Flags: superreview?(lhansen) → superreview+
Assignee | ||
Comment 7•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•