Changes between Initial Version and Version 1 of Ticket #14047, comment 16
- Timestamp:
- Jan 17, 2020, 9:20:06 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14047, comment 16
initial v1 1 Well teamwork ! It makes sense to share the workload, and that way you shared credit ;-) (BBuffer fix credit goes to you; ffmpeg fix credit goes to Michael; we went AHCI thanks to waddlesplash ..etc). I'm still a bit anxious for the leak_analyser to get fixed though (as per comment:9 re runtime_loader), if only to make sure that no one else will get bitten like you were... And in case I myself have more leaks to hunt for in the future. Might ping waddleslplash in a few weeks about it when the dust settles (we're in the process of taming media_addon_server, finding new hardware, and almost returning to production).1 Well... teamwork ! It makes sense to share the workload, and that way you shared credit ;-) (BBuffer fix credit goes to you; ffmpeg fix credit goes to Michael; we went AHCI thanks to waddlesplash ..etc). I'm still a bit anxious for the leak_analyser to get fixed though (as per comment:9 re runtime_loader), if only to make sure that no one else will get bitten like you were... And in case I myself have more leaks to hunt for in the future. Might ping waddleslplash in a few weeks about it when the dust settles (we're in the process of taming media_addon_server, finding new hardware, and almost returning to production). 2 2 Agreed it's good to test with both leak_analyser.sh and plain-old-looking at ProcessController's memory gauges too, as a "final word" to restore peace of mind. In Dane's testing (looking at the gauges) we are leak free.