Closed
Bug 861973
Opened 12 years ago
Closed 12 years ago
STLport shouldn't use its own allocator
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla23
People
(Reporter: glandium, Assigned: glandium)
References
Details
Attachments
(1 file)
|
(deleted),
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
The mochitest-8 oranges i was getting when landing bug 850332 turned out to unveil an issue with the fact that STLport is using its own allocator on top of malloc, and that then using malloc_usable_size() on pointers returned by that allocator (like in http://hg.mozilla.org/mozilla-central/file/53c2e7b9753b/ipc/chromium/src/base/histogram.cc#l418 , where ranges_ is a std::vector) fails because the pointers point inside an allocated range.
|
Assignee | |
Comment 1•12 years ago
|
||
Attachment #737593 -
Flags: review?(ted)
|
||
Comment 2•12 years ago
|
||
Does this affect B2G?
|
||
Comment 3•12 years ago
|
||
Comment on attachment 737593 [details] [diff] [review]
Force STLport not to use its own allocator
Review of attachment 737593 [details] [diff] [review]:
-----------------------------------------------------------------
Ugh.
Attachment #737593 -
Flags: review?(ted) → review+
|
|
Assignee | |
Comment 4•12 years ago
|
||
(In reply to Justin Lebar [:jlebar] from comment #2)
> Does this affect B2G?
B2G has a similar issue, but for a different reason. See bug 850576.
|
|
Assignee | |
Comment 5•12 years ago
|
||
|
||
Comment 6•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
|
||
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•