Bug 1537609 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

A specific link that reproduces this is: https://www.pogo.com/games/lottso-express

A few initial findings:
* We get like 4fps; Chrome runs totally smooth.
* The profiler shows that we're doing multiple major GCs per frame.
* Even before FF66, this appears to be the case, but the GCs got somehow more expensive in FF66
* The games use some form of cheating prevention that, it looks like, inserts tons of `debugger` statements (I guess to thwart naive attempts to modify game state by opening the console?  It's quite circumventable...)

So I think there are three questions to answer here:
1. Is the `debugger` statement causing all the GCs?
2. If so, why (note the console isn't even open) and, if not, what is?
3. Why did the GCs get more expensive with FF66.
A specific link that reproduces this is: https://www.pogo.com/games/lottso-express

A few initial findings:
* We get like 4fps; Chrome runs totally smooth.
* The profiler shows that we're doing multiple major GCs per frame.
* Even before FF66, this appears to be the case, but the GCs got somehow more expensive in FF66
* The games use some form of cheating prevention that, it looks like, inserts tons of `debugger` statements

So I think there are three questions to answer here:
1. Is the `debugger` statement causing all the GCs?
2. If so, why (note the console isn't even open) and, if not, what is?
3. Why did the GCs get more expensive with FF66.
A specific link that reproduces this is: https://www.pogo.com/games/lottso-express

A few initial findings:
* We get like 4fps; Chrome runs totally smooth.
* The profiler shows that we're doing multiple major GCs per frame.
* Even before FF66, this appears to be the case, but the GCs got somehow more expensive in FF66
* The games use some form of cheating prevention that, it looks like, inserts tons of `debugger` statement calls

So I think there are three questions to answer here:
1. Is the `debugger` statement causing all the GCs?
2. If so, why (note the console isn't even open) and, if not, what is?
3. Why did the GCs get more expensive with FF66.

Back to Bug 1537609 Comment 2