I tried the database in another copy of the program (i.e., not this test version), and it froze in 3, 4, 3. I have noticed this multiple times when bouncing from version to version of the program, even from computer to computer (i.e. 2.? on linux, windows, etc.); when it gets acutely worse, it gets acutely worse in all versions. This either must be a fluke, or a really significant hint. It must be!
On Saturday, July 28, 2012 1:00:54 AM UTC-7, Chris wrote: > > Freezes on unlearned cards: 8, 4, 2, 3, 4. This may indicate you have > gotten very close to discovering the issue, insofar as it is way worse; or, > it could just be one of those statistical flukes which has been happening > in this debug process. I will try tomorrow and see if it is > better/worse/similar. > > - Chris Shanks > > On Friday, July 27, 2012 10:11:29 PM UTC-7, Peter Bienstman wrote: >> >> Quoting Chris <the.whistling....@gmail.com>: >> >> > First try, froze after 10 cards, will continue through my scheduled >> cards. >> >> OK, here's test 10: >> >> http://users.ugent.be/~pbienst/pub/mnemosyne-2.0.1-test10-setup.exe >> >> In this version, I've moved even more work from sql to Python. The >> remaining sql is really simple now. If this still hangs, I'll need to >> reactivate the debugging statements again. >> >> Something else to be aware of: there is now one sql query less for >> 'front-to-back only' cards, so it could be that the problem is solved >> for those cards, but not yet for other card types. >> >> Peter >> >> >> -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to mnemosyne-proj-users@googlegroups.com. To unsubscribe from this group, send email to mnemosyne-proj-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msg/mnemosyne-proj-users/-/jqbB2H8qL1MJ. For more options, visit https://groups.google.com/groups/opt_out.
