| 11 Feb 2025 |
 motiejus | So it looks like it's indeed an environment-related issue: https://github.com/blakeblackshear/frigate/discussions/16450#discussioncomment-12152067
The first thing that comes to mind is looking at all the applications loaded into that process, and see if any of them have different versions. While sounds like work, but feels like shooting in the dark a bit.
If anyone has better tips, I am all ears. | 20:45:36 |
| motiejus | * So it looks like it's indeed an environment-related issue: https://github.com/blakeblackshear/frigate/discussions/16450#discussioncomment-12152067
The first thing that comes to mind is looking at all the applications loaded into that process, and see if any of them have different versions. While sounds like work, but feels like wandering in the dark a bit.
If anyone has better tips, I am all ears. | 20:45:51 |
| motiejus | Filed https://github.com/NixOS/nixpkgs/issues/381280 for visibility | 21:13:08 |
| motiejus | * Filed https://github.com/NixOS/nixpkgs/issues/381280 | 21:13:18 |
 @hexa:lossy.network | yeah, well | 21:19:52 |
| @hexa:lossy.network | I'm here | 21:19:53 |
| @hexa:lossy.network | I'm not quite sure where to start debugging this further | 21:20:08 |
| @hexa:lossy.network | multiprocessing is a python standard library module | 21:20:55 |
| @hexa:lossy.network | our python is not compiled with pgo | 21:21:04 |
 K900 | I would start by attaching a profiler | 21:21:28 |
| @hexa:lossy.network | but the problem could also be gomp | 21:21:33 |
| K900 | Like py-spy | 21:21:43 |
| K900 | And then maybe perf if it's not in Python code | 21:21:50 |
| @hexa:lossy.network | there was a perf already | 21:21:59 |
| @hexa:lossy.network | https://github.com/blakeblackshear/frigate/discussions/16450#discussioncomment-12143059 | 21:22:13 |
