2024/10/21

Newest at the top

2024-10-21 03:13:24 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-10-21 03:08:32 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-21 03:07:36 +0200Sgeo(~Sgeo@user/sgeo) Sgeo
2024-10-21 03:05:41 +0200tremon(~tremon@83.80.159.219) (Quit: getting boxed in)
2024-10-21 03:05:22 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-10-21 03:00:52 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-21 02:57:58 +0200 <Axman6> Henson: Are you able to make a minimal reproducer? it sounds like a fairly easy one to reproduce if it's just using async, MVars and foreign pointers.
2024-10-21 02:55:19 +0200xff0x(~xff0x@2405:6580:b080:900:b1c9:c57e:b0f1:f862) (Ping timeout: 264 seconds)
2024-10-21 02:53:28 +0200szkl(uid110435@id-110435.uxbridge.irccloud.com) szkl
2024-10-21 02:50:30 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 276 seconds)
2024-10-21 02:48:24 +0200synchromesh(~john@2406:5a00:2497:300:dd93:cdaa:8c5a:4091) (Ping timeout: 260 seconds)
2024-10-21 02:46:17 +0200synchrom1(~john@2406:5a00:2497:300:dd93:cdaa:8c5a:4091) (Ping timeout: 252 seconds)
2024-10-21 02:46:09 +0200synchrom2(~john@180.148.124.74) synchromesh
2024-10-21 02:45:31 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-21 02:43:40 +0200synchromesh(~john@2406:5a00:2497:300:dd93:cdaa:8c5a:4091) synchromesh
2024-10-21 02:42:33 +0200ai5lk(~ai5lk@209-188-121-236.taosnet.com) (Client Quit)
2024-10-21 02:38:20 +0200Smiles(uid551636@id-551636.lymington.irccloud.com) Smiles
2024-10-21 02:38:05 +0200ai5lk(~ai5lk@209-188-121-236.taosnet.com)
2024-10-21 02:36:23 +0200synchromesh(~john@2406:5a00:2497:300:dd93:cdaa:8c5a:4091) (Ping timeout: 244 seconds)
2024-10-21 02:34:55 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 264 seconds)
2024-10-21 02:33:54 +0200synchrom1(~john@2406:5a00:2497:300:dd93:cdaa:8c5a:4091) synchromesh
2024-10-21 02:31:49 +0200sawilagar(~sawilagar@user/sawilagar) (Ping timeout: 248 seconds)
2024-10-21 02:29:25 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-21 02:22:50 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds)
2024-10-21 02:18:18 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 245 seconds)
2024-10-21 02:14:03 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-21 02:02:57 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-10-21 02:00:02 +0200supercode(~supercode@user/supercode) (Quit: Client closed)
2024-10-21 01:58:10 +0200ljdarj1ljdarj
2024-10-21 01:58:09 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 248 seconds)
2024-10-21 01:55:32 +0200ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2024-10-21 01:55:16 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-21 01:52:32 +0200divya(~user@139.5.10.160) (Read error: Connection reset by peer)
2024-10-21 01:49:32 +0200Smiles(uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2024-10-21 01:49:06 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-10-21 01:47:34 +0200Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Ping timeout: 260 seconds)
2024-10-21 01:46:10 +0200travgm(~username@fsf/member/travgm) (Ping timeout: 252 seconds)
2024-10-21 01:44:46 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-21 01:42:56 +0200supercode(~supercode@user/supercode) supercode
2024-10-21 01:42:29 +0200machinedgod(~machinedg@d50-99-47-73.abhsia.telus.net) (Ping timeout: 252 seconds)
2024-10-21 01:39:08 +0200 <Henson> when using async with multiple threads and the creation/destruction happening on multiple capabilities. If I use "-N1" and restrict Haskell to a single core, it then doesn't happen when using "async". Does anybody have any suggestions as to why this might be happening?
2024-10-21 01:38:08 +0200 <Henson> I'm experiencing what appears to be a memory leak when rapidly creating ForeignPtrs using calloc on one team of threads, and passing them via an MVar to another team of threads that remove them from the MVars an allow them to be GCd with the finalizerFree. This leak does not happen when using Ptrs with an explicit "free". It also doesn't happen when using asyncBound. But it does happen...
2024-10-21 01:36:04 +0200Henson(~kvirc@bras-base-owsdon5915w-grc-09-64-231-69-12.dsl.bell.ca) Henson
2024-10-21 01:35:25 +0200vglfr(~vglfr@c-73-250-25-113.hsd1.md.comcast.net) vglfr
2024-10-21 01:33:42 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 246 seconds)
2024-10-21 01:29:21 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-21 01:24:24 +0200vglfr(~vglfr@2607:fb90:eabf:c341:ad3:f757:4ed5:dde4) (Read error: Connection reset by peer)
2024-10-21 01:23:08 +0200machinedgod(~machinedg@d50-99-47-73.abhsia.telus.net) machinedgod
2024-10-21 01:18:44 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 255 seconds)
2024-10-21 01:16:51 +0200travgm(~username@fsf/member/travgm) travgm