Closed Bug 611053 Opened 14 years ago Closed 10 years ago

File Microsoft Connect bug with linkrepro for compiler crash from bug 591836

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: ted, Assigned: ted)

References

Details

The patch on bug 591836 caused Visual C++ to crash while attempting to compile (in the link phase, due to WPO/PGO) mozjs+xul. Splitting mozjs back out to its own DLL made the crash go away.

We should file a Microsoft Connect bug with a linkrepro that reproduces the crash.

Filing this bug just to have a way to track this.

The changeset that first introduced the crash was 1af8f0c895bc.
Assignee: nobody → ted.mielczarek
Just as a data point, I screwed up and forgot to include a profiling command in my build, so it did a PGO build with no profiling data, and it succeeded. This at least indicates that the problem is specific to optimizing with profiling data.
Ok, I reproduced the crash and produced a linkrepro. The only downside is that it's 2GB worth of files. I guess I'll see how well it compresses!
Was the bug ever reported to
...Microsoft. I will try to reproduce with VS2010 SP1.
No, I had trouble getting the linkrepro into an actual reproducible state.
That is, I could 100% reproduce the compiler crash, and generate a linkrepro, but then I was unsuccessful in trying to reproduce the link using the linkrepro. It seemed to not have its options right or something. I think perhaps the linkrepro mechanism and PGO are not well integrated or something.
I'm clearly never going to get around to this.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.