I can't seem to reproduce this at all anymore. I fired everything up a few hours ago, and try as i did to scan, stop suddenly, delete it or start scanning again, whatever i tried...it slowly got on with the next job i set and all with no crashes. :)
I find following the code itself incredibly difficult (and not just because i'm not used to vala lol), but i thought i'd be helpful and build it with clang to look for outstanding errors (really i was trying to look for some sort of obvious deletion of an already deleted entity. If it's there, it's beyond my abilities to see it.)
I'm surprised this is still happening?
I can't seem to reproduce this at all anymore. I fired everything up a few hours ago, and try as i did to scan, stop suddenly, delete it or start scanning again, whatever i tried...it slowly got on with the next job i set and all with no crashes. :)
I find following the code itself incredibly difficult (and not just because i'm not used to vala lol), but i thought i'd be helpful and build it with clang to look for outstanding errors (really i was trying to look for some sort of obvious deletion of an already deleted entity. If it's there, it's beyond my abilities to see it.)
HOWEVER...aside from a LOT of dead assignments/ initialisations (some/all of which may be false-positives) there are 7 null pointer dereferences in the code and since they're unsafe/ problematic/ apocalyptic, i've put them in bug #1212452 (https:/ /bugs.launchpad .net/ubuntu/ +source/ simple- scan/+bug/ 1212452)