Hi, the log that you generated was generated using menu Help > Debug > Send logs and does include also part of DbgView (last 20 seconds), but from your description it is unclear what is the issue and what has frozen for you? It was not the UI thread (otherwise you couldn't even get to menu Help > Debug).
As soon as you want to change something or click something, MM freezes. The program stops responding.
What exactly do you clicked? If the program stops responding then usually the log should be auto-generated, was this the case for you and did you submit a freeze/crash log? Which log id? Was the MM window dimmed? It could indicate that a dialog/menu is behind the MM window and the dimmed window looks like frozen?
The default freeze timeout is 30 seconds after which the crash/freeze log is auto-generated (you can temporarily lower it in menu Help > Debug > Change freeze timeout)
i.e. once the program stops responding wait 30 seconds for the freeze/crash log generated (it looks exacly like the log that you generated manually via Help > Debug)
and either attach it or submit it and write the log ID here.
Thanks!
Hi, the log that you generated was generated using menu Help > Debug > Send logs and does include also part of DbgView (last 20 seconds), but from your description it is unclear what is the issue and what has frozen for you? It was not the UI thread (otherwise you couldn't even get to menu Help > Debug).
[quote]As soon as you want to change something or click something, MM freezes. The program stops responding.[/quote]
What exactly do you clicked? If the program stops responding then usually the log should be auto-generated, was this the case for you and did you submit a freeze/crash log? Which log id? Was the MM window dimmed? It could indicate that a dialog/menu is behind the MM window and the dimmed window looks like frozen?
The default freeze timeout is 30 seconds after which the crash/freeze log is auto-generated (you can temporarily lower it in menu Help > Debug > Change freeze timeout)
i.e. once the program stops responding wait 30 seconds for the freeze/crash log generated (it looks exacly like the log that you generated manually via Help > Debug)
and either attach it or submit it and write the log ID here.
Thanks!