(Away) Reporter
	Description • 10 years ago

See bug 1023941 comment 32. The summary is that xulrunner from VS2013 won't work on XP SP2 unless it stops calling malloc from the main exe (from DLLs is fine).

This one looks less straightforward than bug 1060115. nsXULRunnerApp.cpp has a fair amount of stuff in it. nsINIParser is one source of malloc; I haven't looked into the others.

How important is this? Should I spend more time figuring out the dependencies? I guess an alternative is to not switch over the xulrunner builders, but that seems kinda yucky.

	(not currently active) Ted Mielczarek
	Comment 1 • 10 years ago

I don't think this is important, we're not shipping a xulrunner product. We primarily only ship these builds to use as the SDK for building binary components for Firefox, and that should work fine.

	Mike Hommey [:glandium]
	Comment 2 • 10 years ago

Plus, we plan to kill xulrunner entirely.

	Benjamin Smedberg
	Comment 3 • 10 years ago

Don't spend time on this. We should switch XR to the new compiler and not care about XPSP2 in this case.

	(no longer active)
	Comment 4 • 10 years ago

Should we remove the dependency on bug 914596?

	(Away) Reporter
	Comment 5 • 10 years ago

Sure, why not. I'm tempted to mark it altogether WONTFIX, but using |new| (per bug 1060115 comment 8) might make this easier if someone really wanted to spend time on it.

	Chris Cooper [:coop] (he/him)
	Comment 6 • 7 years ago

Mass close of build system-related xulrunner bugs.