-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Fix illegal invocation error on final harvest #594
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent job diagnosing this
Codecov Report
@@ Coverage Diff @@
## main #594 +/- ##
==========================================
+ Coverage 67.54% 68.12% +0.58%
==========================================
Files 132 129 -3
Lines 5907 5993 +86
Branches 1084 1141 +57
==========================================
+ Hits 3990 4083 +93
Misses 1547 1547
+ Partials 370 363 -7
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 13 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Asset Size ReportMerging this pull request will result in the following CDN asset size changes:
Merging this pull request will result in the following NPM package consumer size changes:
Other Standard CDN AssetsReleased Assets
Built Assets
Other Polyfill CDN AssetsReleased Assets
Built Assets
|
An issue from 1.234.0 has been addressed in which an illegal invocation error could occur during a final harvest as a result of calling
addPageAction
and passingwindow.location
as an argument before a navigation.Overview
Reverting a change from #521. Calling
addPageAction
and passingwindow.location
as an argument before a navigation would result in calling.toString
on the globalwindow.location
. Doing so during a page unload causes anIllegal Invocation
error due to the globalwindow.location.toString()
losing it's context.Related Issue(s)
https://issues.newrelic.com/browse/NEWRELIC-9370
Testing
Test added to ensure this issue does not happen again.