1205225 - MSVC2015 internal error compiling js part

Status: RESOLVED WORKSFORME

(Firefox Build System :: General, defect)

Description

[Xidorn Quan [:xidorn] UTC+10]

Attachment: build output

I frequently run into internal error when compiling js part of Firefox with MSVC2015.

The attachment shows an example of such internal error.

I meet this error almost every time when I update the local tree. Executing 'mach build' again would make it actually finish.

My .mozconfig for the attached log:

ac_add_options --enable-application=browser
ac_add_options --enable-accessibility
ac_add_options --enable-debug
ac_add_options --enable-warnings-as-errors

ac_add_options --disable-crashreporter
ac_add_options --disable-updater
ac_add_options --disable-installer
ac_add_options --disable-maintenance-service

mk_add_options AUTOCLOBBER=1
mk_add_options MOZ_PACKAGE_JSSHELL=1
mk_add_options MOZ_PSEUDO_DERECURSE=1
mk_add_options MOZ_MAKE_FLAGS=-j7

ac_add_options --target=x86_64-pc-mingw32
ac_add_options --host=x86_64-pc-mingw32
ac_add_options --disable-optimize

Comment 1

[(not currently active) Ted Mielczarek]

You should report this to Microsoft at https://connect.microsoft.com/. If you can reliably reproduce it you should provide STR. You may be able to use /LINKREPRO to generate a testcase for Microsoft, described here:
https://support.microsoft.com/en-us/kb/974229

Comment 2

[Xidorn Quan [:xidorn] UTC+10]

I believe I can reproduce this every time if I do clobber before build... I don't have a finer-grained STR, though.

Comment 3

[Xidorn Quan [:xidorn] UTC+10]

FWIW, it seems chromium meets this issue as well. See https://code.google.com/p/chromium/issues/detail?id=482671 and they've reached Microsoft for it.

Comment 4

[(no longer active)]

(In reply to Xidorn Quan [:xidorn] (UTC+8) from comment #3)
> FWIW, it seems chromium meets this issue as well. See
> https://code.google.com/p/chromium/issues/detail?id=482671 and they've
> reached Microsoft for it.

May compiler ICE bugs may look similar, it'd still be really nice if you can report the bug you're seeing to Microsoft.  Let them figure out if that is the same issue as what Chromium has been seeing.

Look at it this way, if you don't report the bug, it may not get fixed.  :-)

Comment 5

[Xidorn Quan [:xidorn] UTC+10]

I believe I haven't seen this issue since I upgraded to VS2015 Update 1. So it seems this issue has been fixed by Microsoft.