Attachment nvda before restart.log.txt added by PZajda on 2012-04-23 18:02
Description:
NVDA's first run log.
Update:
File added from Trac

Attachment nvda after restart.log.txt added by PZajda on 2012-04-23 18:03
Description:
NVDA's log, after I pressed Alt+Ctrl+N.
Update:
File added from Trac

Comment 2 by PZajda on 2012-04-24 18:59
Hi,

There are still errors when starting NVDA even after last commit. I think there are less error, but there are some.
Attached is another log.

Attachment nvda.log.txt added by PZajda on 2012-04-24 19:00
Description:
Update:
File added from Trac

Comment 3 by briang1 on 2012-04-24 19:25
Hmm, is your machine running slowly during these events. a lot of watchdog activity going on.
I also wonder about the avg software as it used to slug start up mega when I used it, and who knows what that might do.
Just a thought.

Comment 4 by PZajda on 2012-04-24 22:41
Hi,

I'm OK about the time when others softwares are starting. But in that case, NVDA stays very slow even when starting is finished.
And I have some "Error registering class object" in the log until I restart NVDA.

Comment 5 by mdcurran (in reply to comment description) on 2012-04-25 05:15
Replying to PZajda:

I have set NVDA to run automaticaly before and after I open a session.

When everything is started, I have to restart NVDA because I have so much freezes.

In reference to your NVDA before restart log:

• How long as this slowness/freezing been happening? only since the win8Injection merge, or since 2011.3?
• Just checking, but you don't always run NVDA with logging set to debug do you? we would never advize this as this will always be extremely slow. For normal use we always recommend log level of info.
• Can you tell me what the following applications are:
  • TosA2dp.exe
  • TosBtHSP.exe
  • TosBtMng.exe

Comment 6 by PZajda (in reply to comment 5) on 2012-04-25 06:58
Replying to mdcurran:

Replying to PZajda:

I have set NVDA to run automaticaly before and after I open a session.

When everything is started, I have to restart NVDA because I have so much freezes.

In reference to your NVDA before restart log:

• How long as this slowness/freezing been happening? only since the win8Injection merge, or since 2011.3?

It is since win8Injection merge.

• Just checking, but you don't always run NVDA with logging set to debug do you? we would never advize this as this will always be extremely slow. For normal use we always recommend log level of info.

No, I don't always run NVDA with logging set to debug, I usualy set it to info.

• Can you tell me what the following applications are:
  • TosA2dp.exe
  • TosBtHSP.exe
  • TosBtMng.exe

These programmes are part of my bluetooth software.
I hadn't any problem before win8Injection.

Comment 7 by PZajda on 2012-05-09 14:08
Hi,

I tryed with the main-5177 from bzr and with 2012.1 which worked before win8Injection and I only have error with the main-5177. I have to restart NVDA because it is very long to do something.

Attached is a log file with the errors I had today.

Attachment nvda.2.log.txt added by PZajda on 2012-05-09 14:12
Description:
NVDA log file (05/09/2012)
Update:
File added from Trac

@pzajda are these issues still occurring for you? Also, @michaelDCurran do the logs provided offer anything useful, or do you believe this is of fault of some Bluetooth software as indicated in #2261 (comment)

Are there any further discussions regarding to this issue? Is it still occuring?

I cannot see the log files, but it might be related to #7982 and referenced issues.
Please note the comments provided by @dineshkaushal.

@Adriani90, I have attached the files it the comments above.
Also, it would be good to know if these issues are still occurring for @pzajda. Otherwise, I am leaning toward an invalid.

@ehollig, after looking at the log files, this could be probably solved by registering the com dlls which can be done by using the tool provided in NVDA 2018.2. Who is the author of this issue? Is it still reproducible?

Hello @Adriani90. Thank you for looking at the log files. I believe the original author is @pzajda based on the Trac username. However, based on the age of this issue and a possible solution is available, I will close this issue.