Change:
debugging my nextjs project to find out which component is slowing down my application by using react devtools profiler section. when i start recording by clcking the blue button it start recording. then when go to my page and navigate different page like first i sign in to my application and then navigate from home to my when i stop the recording this error occured. Every time react-devtools-extensions 2- Could not find node with id "464" in commit tree
best of luck
Hi thank you for reporting. should fix this. It's scheduled to be included in DevTools 6.0.0. Let us know if it's still happening in 6.0.0

Discussion:
}; onProfilingStatus: (isProfiling: boolean) => void = isProfiling => { <ins> if (this._isProfiling === isProfiling) { return; } </ins> if (isProfiling) { this._dataBackends.splice(0); this._dataFrontend = null;

}); } <del> if (this._isProfiling !== isProfiling) { this._isProfiling = isProfiling; </del> <ins> this._isProfiling = isProfiling; </ins> <del> // Invalidate suspense cache if profiling data is being (re-)recorded. // Note that we clear again, in case any views read from the cache while profiling. // (That would have resolved a now-stale value without any profiling data.) this._cache.invalidate(); </del> <ins> // Invalidate suspense cache if profiling data is being (re-)recorded. // Note that we clear again, in case any views read from the cache while profiling. // (That would have resolved a now-stale value without any profiling data.) this._cache.invalidate(); </ins> <del> this.emit('isProfiling'); </del> <ins> this.emit('isProfiling'); </ins> <del> // If we've just finished a profiling session, we need to fetch data stored in each renderer interface // and re-assemble it on the front-end into a format (ProfilingDataFrontend) that can power the Profiler UI. // During this time, DevTools UI should probably not be interactive. if (!isProfiling) { this._dataBackends.splice(0); this._rendererQueue.clear(); </del> <ins> // If we've just finished a profiling session, we need to fetch data stored in each renderer interface // and re-assemble it on the front-end into a format (ProfilingDataFrontend) that can power the Profiler UI. // During this time, DevTools UI should probably not be interactive. if (!isProfiling) { this._dataBackends.splice(0); this._rendererQueue.clear(); </ins> <del> // Only request data from renderers that actually logged it. // This avoids unnecessary bridge requests and also avoids edge case mixed renderer bugs. // (e.g. when v15 and v16 are both present) this._rendererIDsThatReportedProfilingData.forEach(rendererID => { if (!this._rendererQueue.has(rendererID)) { this._rendererQueue.add(rendererID); </del> <ins> // Only request data from renderers that actually logged it. // This avoids unnecessary bridge requests and also avoids edge case mixed renderer bugs. // (e.g. when v15 and v16 are both present) this._rendererIDsThatReportedProfilingData.forEach(rendererID => { if (!this._rendererQueue.has(rendererID)) { this._rendererQueue.add(rendererID); </ins> <del> this._bridge.send('getProfilingData', {rendererID}); } }); </del> <ins> this._bridge.send('getProfilingData', {rendererID}); } }); </ins> <del> this.emit('isProcessingData'); } </del> <ins> this.emit('isProcessingData'); </ins> } }; }