PDF-XChange Lite V7 => CPU SOLVED
Moderators: TrackerSupp-Daniel, Tracker Support, Paul - Tracker Supp, Vasyl-Tracker Dev Team, Chris - Tracker Supp, Sean - Tracker, Ivan - Tracker Software, Tracker Supp-Stefan
PDF-XChange Lite V7 => CPU
Windows 7 64-bit
Word 2010 32-bit
If I select PDF-XChange Lite V7 323.2 as printer in Word, CPU usage of Word jumps from 0% to 40%. Additionally splwow64.exe goes from 0% to 4% and Windows 7 sidebar.exe (I use the desktop watch) from 0% to 3%. Obvious sign is the cursor (mouse and keyboard) constantly flickering in Word from the CPU load. I cannot work like that. This was not the case with V6.
It does not make a difference, if I switch the PDF-XChange printer settings from Auto to GDI or XPS.
If I switch to another printer driver in Word, everything goes back to normal.
I have PDF-XChange Lite as standard printer in Windows and outside of Word I do not see this problem.
Word 2010 32-bit
If I select PDF-XChange Lite V7 323.2 as printer in Word, CPU usage of Word jumps from 0% to 40%. Additionally splwow64.exe goes from 0% to 4% and Windows 7 sidebar.exe (I use the desktop watch) from 0% to 3%. Obvious sign is the cursor (mouse and keyboard) constantly flickering in Word from the CPU load. I cannot work like that. This was not the case with V6.
It does not make a difference, if I switch the PDF-XChange printer settings from Auto to GDI or XPS.
If I switch to another printer driver in Word, everything goes back to normal.
I have PDF-XChange Lite as standard printer in Windows and outside of Word I do not see this problem.
- Tracker Supp-Stefan
- Site Admin
- Posts: 17824
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
- Contact:
Re: PDF-XChange Lite V7 => CPU
Hello ChrisZ16,
Does this happen only while you have Word "printing" to the Lite driver, or does the CPU load continue even after the print job has completed, and you try to continue working with Word?
Regards,
Stefan
Does this happen only while you have Word "printing" to the Lite driver, or does the CPU load continue even after the print job has completed, and you try to continue working with Word?
Regards,
Stefan
Re: PDF-XChange Lite V7 => CPU
Hello Stefan,
It is all the time like that, independent of printing. Right from the start of Word, until I select another printer.
Regards
Chris
It is all the time like that, independent of printing. Right from the start of Word, until I select another printer.
Regards
Chris
Re: PDF-XChange Lite V7 => CPU
I have exactly the same problem but with PDF-XChange Standard
It's impossible to lead us astray for we don't care even to choose the way.
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
-
- User
- Posts: 2347
- Joined: Wed Jan 18, 2006 12:10 pm
Re: PDF-XChange Lite V7 => CPU
At first sight, I do not have the problem with the 32-bit version of PDF-XChange Standard (build 323) nor -Lite Free (build 323.2).
As a work-around, you can think about activating the AutoUnload parameter that will automatically stop the printer after max. 30 seconds.
(via right mouse click on the pdf-xchange printer icon in the Windows System Tray = right side of the Task bar, and then click Settings)
Regards.
As a work-around, you can think about activating the AutoUnload parameter that will automatically stop the printer after max. 30 seconds.
(via right mouse click on the pdf-xchange printer icon in the Windows System Tray = right side of the Task bar, and then click Settings)
Regards.
Re: PDF-XChange Lite V7 => CPU
Thanks for your time, Willy, and Merry Christmas!
I do not have any printer icons in the Windows System Tray, so I assume you mean the pdfSaver icon? I don't have pdfSaver running, I always uncheck it on installation (also in earlier V6, was no problem). But the .exe is here, so I started it manually and tried your work-around, but it did not help. pdfSaver starts and auto-unloads after 30 secs (but I anyway don't have it running normally), the CPU load stays the same.
BTW: The list of installed printers in Windows shows "PDF-XChange Lite V6", but in the properties it says "Version 7.0 (Build 323.2)". I guess this is only a naming thing? I have the registered version of PDF-XChange Editor V7 323.2 and the PDF-XChange Lite, that comes with it.
Regards
Chris
I do not have any printer icons in the Windows System Tray, so I assume you mean the pdfSaver icon? I don't have pdfSaver running, I always uncheck it on installation (also in earlier V6, was no problem). But the .exe is here, so I started it manually and tried your work-around, but it did not help. pdfSaver starts and auto-unloads after 30 secs (but I anyway don't have it running normally), the CPU load stays the same.
BTW: The list of installed printers in Windows shows "PDF-XChange Lite V6", but in the properties it says "Version 7.0 (Build 323.2)". I guess this is only a naming thing? I have the registered version of PDF-XChange Editor V7 323.2 and the PDF-XChange Lite, that comes with it.
Regards
Chris
Re: PDF-XChange Lite V7 => CPU
Hi, Stefan!
This happens immediately after PDF-XChange Standard was chosen in Word's print dialog
This happens immediately after PDF-XChange Standard was chosen in Word's print dialog
It's impossible to lead us astray for we don't care even to choose the way.
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
-
- User
- Posts: 2347
- Joined: Wed Jan 18, 2006 12:10 pm
Re: PDF-XChange Lite V7 => CPU
Also a Merry Christmas to everyone.
Sorry, I totally misunderstood the problem. I thought it was the printing process that kept hanging.
The problem is rather with the interaction between Microsoft Word and the default printer. In this case, PDF-XChange Standard or Lite.
From the moment that you start Word, it interacts with the printer about fonts that can be used, page layout, ...
I do not know if you are using some uncommon default font in your documents, or a page format that is different from the printer's default ...
Do you have the problem with all your documents or just with some specific documents.
You might also post a sample document to see if the problem is reproducible at someone else's side.
Myself, I do not see any delay while typing in Word 2010 whilst PDF-XChange Standard printer (V7 323 - Nov. 30, 2017) is set as default printer.
Best regards.
Sorry, I totally misunderstood the problem. I thought it was the printing process that kept hanging.
The problem is rather with the interaction between Microsoft Word and the default printer. In this case, PDF-XChange Standard or Lite.
From the moment that you start Word, it interacts with the printer about fonts that can be used, page layout, ...
I do not know if you are using some uncommon default font in your documents, or a page format that is different from the printer's default ...
Do you have the problem with all your documents or just with some specific documents.
You might also post a sample document to see if the problem is reproducible at someone else's side.
Myself, I do not see any delay while typing in Word 2010 whilst PDF-XChange Standard printer (V7 323 - Nov. 30, 2017) is set as default printer.
Best regards.
Re: PDF-XChange Lite V7 => CPU
Thank you for reply, Willy!
This happen even with empty document. I just change printer to PDF-XChange Standard.
So far this happens only with MS Office.
This happen even with empty document. I just change printer to PDF-XChange Standard.
So far this happens only with MS Office.
It's impossible to lead us astray for we don't care even to choose the way.
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
-
- User
- Posts: 2347
- Joined: Wed Jan 18, 2006 12:10 pm
Re: PDF-XChange Lite V7 => CPU
What you still can do to raise the performance of Word is:
1) turn off Auto-correct
2) turn off automatic Grammar and Spelling check
3) turn off (all) "Auto-format as you Type" options
1) turn off Auto-correct
2) turn off automatic Grammar and Spelling check
3) turn off (all) "Auto-format as you Type" options
Re: PDF-XChange Lite V7 => CPU
Same here - it happens with every document, even with an empty one.
Regarding turning off Auto-correct, automatic Grammar and Spelling check, (all) "Auto-format as you Type" - most of these are turned off anyway. I also turned off the remaining ones. It did not change anything.
To point out again: The CPU-load does not happen with V6, which I use for years. It is a problem with V7.
Regards
Chris
Regarding turning off Auto-correct, automatic Grammar and Spelling check, (all) "Auto-format as you Type" - most of these are turned off anyway. I also turned off the remaining ones. It did not change anything.
To point out again: The CPU-load does not happen with V6, which I use for years. It is a problem with V7.
Regards
Chris
Re: PDF-XChange Lite V7 => CPU
+1ChrisZ16 wrote: To point out again: The CPU-load does not happen with V6, which I use for years. It is a problem with V7.
PS Merry Christmas to everyone!
It's impossible to lead us astray for we don't care even to choose the way.
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
- Tracker Supp-Stefan
- Site Admin
- Posts: 17824
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
- Contact:
Re: PDF-XChange Lite V7 => CPU
Hi everyone!
Hope you all had a lovely Christmas!
I will now pass this to our devs and ask them to look at why this is happening!
Cheers,
Stefan
Hope you all had a lovely Christmas!
I will now pass this to our devs and ask them to look at why this is happening!
Cheers,
Stefan
Re: PDF-XChange Lite V7 => CPU
Thank you Stefan!
It's impossible to lead us astray for we don't care even to choose the way.
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
- Tracker Supp-Stefan
- Site Admin
- Posts: 17824
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
- Contact:
Re: PDF-XChange Lite V7 => CPU
Hello OVG,
I have some further news - apparently we had managed to reproduce this on a development machine, and my colleagues will now investigate why this is happening and try to resolve it asap!
Cheers,
Stefan
I have some further news - apparently we had managed to reproduce this on a development machine, and my colleagues will now investigate why this is happening and try to resolve it asap!
Cheers,
Stefan
Re: PDF-XChange Lite V7 => CPU
Hello Stefan!
Thank so much for informing me!
The Tracker-Software's support is one of the best!
WBR, Oleg
Thank so much for informing me!
The Tracker-Software's support is one of the best!
WBR, Oleg
It's impossible to lead us astray for we don't care even to choose the way.
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
- Tracker Supp-Stefan
- Site Admin
- Posts: 17824
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
- Contact:
- Roman - Tracker Supp
- Site Admin
- Posts: 303
- Joined: Sun Nov 21, 2004 3:19 pm
Re: PDF-XChange Lite V7 => CPU SOLVED
Hi All,
The issue has been resolved (assuming all the reported cases are caused by the problem we managed to reproduce).
As a temporary workaround please delete the registry value "Default DevMode" under the key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\<printer name>" (e.g. "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\PDF-XChange Standard").
To do this you can use Windows Registry Editor (regedit.exe) or a console command like this (run with elevated permissions (as Administrator)):
UPDATE:
Print Spooler service restart is required after this change.
Use Windows Services snap-in or console command like this (run with elevated permissions (as Administrator)):
The issue has been resolved (assuming all the reported cases are caused by the problem we managed to reproduce).
As a temporary workaround please delete the registry value "Default DevMode" under the key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\<printer name>" (e.g. "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\PDF-XChange Standard").
To do this you can use Windows Registry Editor (regedit.exe) or a console command like this (run with elevated permissions (as Administrator)):
Code: Select all
reg delete "HKLM\SYSTEM\CurrentControlSet\Control\Print\Printers\PDF-XChange Standard" /v "Default DevMode" /f
Print Spooler service restart is required after this change.
Use Windows Services snap-in or console command like this (run with elevated permissions (as Administrator)):
Code: Select all
net stop spooler && net start spooler
Re: PDF-XChange Lite V7 => CPU
Hello Roman!
For me problem is gone!!
Great job, thank you (all team) so much!!!
For me problem is gone!!
Great job, thank you (all team) so much!!!
Last edited by Ovg on Wed Jan 10, 2018 5:00 am, edited 1 time in total.
It's impossible to lead us astray for we don't care even to choose the way.
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
PDF-XChange PRO, 10.1.1 (Build 381) / W7 SP1 x64
- TrackerSupp-Daniel
- Site Admin
- Posts: 8440
- Joined: Wed Jan 03, 2018 6:52 pm
Re: PDF-XChange Lite V7 => CPU
Dan McIntyre - Support Technician
Tracker Software Products (Canada) LTD
+++++++++++++++++++++++++++++++++++
Our Web site domain and email address has changed as of 26/10/2023.
https://www.pdf-xchange.com
Support@pdf-xchange.com
Tracker Software Products (Canada) LTD
+++++++++++++++++++++++++++++++++++
Our Web site domain and email address has changed as of 26/10/2023.
https://www.pdf-xchange.com
Support@pdf-xchange.com
- Roman - Tracker Supp
- Site Admin
- Posts: 303
- Joined: Sun Nov 21, 2004 3:19 pm
Re: PDF-XChange Lite V7 => CPU
Hello Ovg,
Thank you for the feedback and you are right - I forgot to mention that Print spooler service needs to be restarted after that registry change.
I will update my previous post.
Thank you for the feedback and you are right - I forgot to mention that Print spooler service needs to be restarted after that registry change.
I will update my previous post.
Re: PDF-XChange Lite V7 => CPU
Confirmed - The problem is gone!
Thank you very much!
Regards
Chris
Thank you very much!
Regards
Chris
- Tracker Supp-Stefan
- Site Admin
- Posts: 17824
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
- Contact: