You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Eliminate base64 allocation hotspots in Socket.js paused data handling
- Store decoded Buffer objects directly in _pausedDataEvents instead of base64 strings
- Avoid repeated base64 decode/encode cycles when recovering paused data
- Update type annotations to reflect buffer storage
- Maintain base64 conversion only for final bridge communication
This eliminates GC pressure from base64 string allocations during pause/resume cycles
0 commit comments