jasmine: toHaveBeenCalledWith() crashes test environment when matching large objects

Problem: toHaveBeenCalledWith() matcher with large objects

Outcome: crashes the entire environment (PhantomJS) or runs recursively (Chrome).

Workaround create a custom equality tester (jasmine.addCustomEqualityTester) before “toHaveBeenCalledWith()” is called. This leads to the EqualityTester failing rather than the environment crashing 😃

Setup:

• Angular2
• Jasmine 2.5.2

Example:

Some sort of injectable service

@Injectable()
class EventService {
    broadcast(name: string, ...args: any[]) {
		//do something
	}
}

A big/complex object to match like an Angular component

class Angular2Component {

	someFunction() {
		injectedEventService.broadcast("myEventName", this);	//this being the component itself
	}

}

Now the Test

describe(() => {

    it("myTest", inject([EventService], (eventService: EventService) => {
	
		spyOn(eventService, "broadcast");
		//createComponent
		component.someFunction();
		
		expect(eventService.broadcast).toHaveBeenCalled(); // true

		// When the second argument isn't passed, the equlity matcher crashes the 
                // environment
		expect(eventService.broadcast).toHaveBeenCalledWith("myEventName")
	
                // Also crashes the environment when the argument amount is correct but one value is
                // not correct
                expect(eventService.broadcast).toHaveBeenCalledWith("someOtherEventName", jasmine.any(Angular2Component));

	}));

})