Search
Saturday, 16th of September 2017, 1:14:58 UTC
6:26:51
beach
Good morning everyone!
9:48:14
jackdaniel
huh, `SPATIAL-TREES internal error: please report how you got this.'
9:48:31
jackdaniel
indeed, how did I do this? ^^
10:26:17
edgar-rft
Dear spatial-tree developers, I got this error because I used spatial-trees.
10:59:09
edgar-rft
No matter who wrote it, authors of meaningless error messages have deserved meaningless bug reports.
11:30:54
jackdaniel
well, it wasn't that meaningless, I've pasted only top header
11:31:14
jackdaniel
condition type was invalid-invariant and whole tree was printed
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)
Saturday, 16th of September 2017, 13:14:58 UTC