On 22 July 2012 04:29, Scott Youngman <[email protected]> wrote: > I think there are two other indications that the problem is not in the > cards themselves. First, Peter has examined decks from some users who have > experienced the problem, and he hasn't reported anything wrong in their > structure. Second, decks which hang in one person's computer don't hang in > another user's computer. >
Ah, okay. Well that's a shame, as it makes it so much harder to debug. Are you saying then that even if you create a blank database with 10 dummy cards, Mnemosyne will eventually hang even on that deck? Or only decks with some picture/audio cards, etc? Have you tried using a tool like Process Hacker (replacement for Windows task manager) to examine the hung Mnemosyne process? If you get it to hang, then double-click the Mnemosyne process in Process Hacker and go to the "threads" tab, you'll see a list of the different threads and can look at the call stack of each one. I'm not sure if you reported whether the hang was a CPU-hogging infinite loop, or a deadlock or some other bad blocking situation, but this could help to find out. You might find the main thread is waiting on a call to Qt or sqlite which never completes? The call traces aren't too long, so I'm sure it would be helpful to post them here. Oisín -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
