make package fails for leak test builds for Windows 64-bit builds

RESOLVED INCOMPLETE

Status

Firefox Build System
General
--
critical
RESOLVED INCOMPLETE
7 years ago
5 months ago

People

(Reporter: armenzg, Unassigned)

Tracking

Trunk
x86_64
Windows Server 2008
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [debug win64])

(Reporter)

Description

7 years ago
Not sure if make package problems are part of Build:Config or of some other packaging component.

I won't be able to enable leak test builds until this gets fixed.

  adding: defaults/profile/prefs.js (172 bytes security) (deflated 35%)
  adding: greprefs.js (172 bytes security) (deflated 74%)
### ERROR: WalkStack64: The handle is invalid.

### ERROR: WalkStack64: The handle is invalid.

### ERROR: WalkStack64: The handle is invalid.

### ERROR: SymGetModuleInfo64: The specified module could not be found.
...

### ERROR: WalkStack64: The handle is invalid.

### ERROR: SymGetModuleInfo64: The specified module could not be found.

### ERROR: WalkStack64: The handle is invalid.

....


Assertion failure: info->entries * 2 == new_stack_buffer_size, at e:/builds/moz2_slave/m-cen-w64-dbg/build/tools/trace-malloc/lib/nsTraceMalloc.c:1014
make[2]: Leaving directory `/e/builds/moz2_slave/m-cen-w64-dbg/build/obj-firefox/browser/installer'
make[1]: Leaving directory `/e/builds/moz2_slave/m-cen-w64-dbg/build/obj-firefox/browser/installer'
make[2]: *** [make-package] Error 3
make[1]: *** [all] Error 2
make: *** [package] Error 2
program finished with exit code 2
elapsedTime=29.280000
Can you give us a link to a full tinderbox log where this happens? It looks like this might be erroring in tracemalloc while running xpcshell to generate the startupcache.
(Reporter)

Comment 2

7 years ago
I have triggered this on staging again since I can't find the full log.
(Reporter)

Updated

7 years ago
Blocks: 669384
(Reporter)

Updated

7 years ago
Whiteboard: debug win64
(Reporter)

Updated

7 years ago
Whiteboard: debug win64 → [debug win64]
(Reporter)

Comment 4

7 years ago
Any chance you (or someone else) could look into helping this be moved forward?
This looks like a problem in tracemalloc. Anyone I could think of to ask about this is already CCed.
I'm seeing this reliably on my 64bit debug builds.
Since trace-malloc is no longer enabled in automation builds, we're unlikely to fix this before trace-malloc is removed by bug 1014341.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INCOMPLETE

Updated

5 months ago
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.