Search
Saturday, 16th of September 2017, 12:28:04 UTC
12:35:58
jackdaniel
\o/, it seems I have found the solution for asynchronous writes after three days of debugging
12:37:03
jackdaniel
or, to be exact, places which need to have locks on them
12:58:29
jackdaniel
thanks, now I need to make it somewhat more fine-grained solution
12:59:14
jackdaniel
no avoid locks over too big chunks of code
12:59:26
jackdaniel
so I need to introduce *more* locks (i.e per-medium)
13:00:43
jackdaniel
what was somewhat puzzling with this issue is that basically there were two causes leading to a very similar results
13:01:00
jackdaniel
1) asynchronous writes to recording streams can corrupt output record history
13:01:23
jackdaniel
2) asynchronous draws mix clipping-regions, so some output-records are not drawn
13:01:54
beach
Yeah, that would make it hard to find.
13:02:09
jackdaniel
so tinkering with 1) or 2) didn't lead to any difference niticeable on the screen
13:03:27
jackdaniel
(there was also third thing, that for standalone-event-loop initial redisplay-frame was called from a thread, so there was a race too, but that was pretty straightforward)
14:23:53
slyrus
jackdaniel: I got one of those spatial trees error messages the other day too
14:27:33
jackdaniel
I was preemptively happy, now I have deadlocks :) I know which parts of code, but I don't know yet how to lock them gracefully
14:28:13
jackdaniel
beach: no worries, last two days I was bumping my head against the wall, now I know what is wrong
14:28:26
jackdaniel
so I'm still fired about this
14:28:39
slyrus
ACTION is still bumping his head against a different wall
14:28:40
beach
That's the good attitude.
14:29:09
beach
slyrus: What wall is that? Curing cancer?
14:30:48
slyrus
no, well, that too, but in the meantime, it's not CLIM-related, but rather some nasty bug in fukamachi's web stack that keeps killing my web app
19:14:58
jackdaniel
I'm not a big fan of LETF macro
Sunday, 17th of September 2017, 0:28:04 UTC