Restore MOZ_STORAGE_MEMORY for system jemalloc

RESOLVED FIXED in mozilla33

Status

()

Toolkit
Storage
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: Jan Beich, Assigned: Jan Beich)

Tracking

Trunk
mozilla33
All
FreeBSD
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

4 years ago
Created attachment 8441779 [details] [diff] [review]
fix

Bug 938730 disabled MOZ_STORAGE_MEMORY for system sqlite. But it didn't take into account MOZ_MEMORY is also defined when system jemalloc is (auto)detected. With system jemalloc there's only one allocator and it's the default one.

For one, FreeBSD 10.0-RELEASE has jemalloc-3.4.0 as the default allocator and which can replace memory/jemalloc.
Attachment #8441779 - Flags: review?(mh+mozilla)
(Assignee)

Comment 1

4 years ago
Comment on attachment 8441779 [details] [diff] [review]
fix

https://tbpl.mozilla.org/?tree=Try&rev=db0708dbb4a1
Attachment #8441779 - Flags: review?(mh+mozilla) → review+
(Assignee)

Updated

4 years ago
Keywords: checkin-needed
The Try run has 2 red builds  with

LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt 

is this related to the patch here ?
https://hg.mozilla.org/integration/mozilla-inbound/rev/d06ae272ade3
Assignee: nobody → jbeich
Keywords: checkin-needed
(Assignee)

Comment 4

4 years ago
(In reply to Carsten Book [:Tomcat] from comment #2)
> The Try run has 2 red builds  with
> 
> LINK : fatal error LNK1123: failure during conversion to COFF: file invalid
> or corrupt 
> 
> is this related to the patch here ?

Sorry, I've wanted to retrigger the jobs but level 1 access doesn't seem to be enough. Those errors were of course unrelated. The patch risk is low: either broken build (typos, #error in mozmemory.h) or regressing bug 938730 (operator precedence).
https://hg.mozilla.org/mozilla-central/rev/d06ae272ade3
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
You need to log in before you can comment on or make changes to this bug.