| 11 Feb 2025 |
 @hexa:lossy.network | yes, for me. | 14:20:26 |
| @hexa:lossy.network | if not for you. | 14:20:31 |
| @hexa:lossy.network | thanks for debugging this with the upstream | 14:21:28 |
| @hexa:lossy.network | frigate 0.15 depends on https://github.com/NixOS/nixpkgs/pull/380543/commits/b3def7466fa7f0389c0df2246dce02887f94509c | 14:21:44 |
 motiejus |
Josh's suggestion is correct that something is not installed or configured the same way as it is in the docker container
:/
| 14:44:20 |
| motiejus | so I guess my next step would be to run this in a Docker container and see if I get the same | 14:54:43 |
| motiejus | * so I guess my next step would be to run this in a Docker container and see if I get the same behavior | 14:54:48 |
| 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 |
| K900 | I'm pretty sure all the interesting bits are too small to see on this graph | 21:23:35 |
| @hexa:lossy.network | yeah, agreed | 21:23:42 |
| K900 | Because gompbarrierwait_end just waits on a bunch of threads | 21:24:19 |
| K900 | https://github.com/gcc-mirror/gcc/blob/master/libgomp/config/posix/bar.c#L73-L105 | 21:24:20 |
| @hexa:lossy.network | motiejus: so can you zoom into what happens before that ends? | 21:25:39 |
| K900 | Also, which threads was that even recorded form | 21:25:56 |
| K900 | * Also, which threads was that even recorded from | 21:25:58 |
| K900 | I wonder if we're just not seeing any of the worker threads | 21:26:04 |
