Announcement

Collapse
No announcement yet.

Foxit Proxy Server causing max CPU workload.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bug Foxit Proxy Server causing max CPU workload.

    Troubleshooting a very sluggish workstation, I found that the program FoxitProxyServer_Socket_RD.exe was utilizing all the CPU (97% CPU usage). I performed an uninstallation and reinstallation of Foxit Reader and this seems to have cleared up the issue.
    I just wanted to make you aware of this issue.

  • #2
    Hi DerekB,

    Thank you for bringing the issue to our attention. Could you please confirm the version of Foxit Reader and your operating system type?


    Comment


    • #3
      Doris,

      This is on Windows 7 Pro x64
      Foxit Reader 9.0.1.1049

      Comment


      • #4
        I have also come across this issue since installing last week. But this is on a terminal server so there were multiple copies of the process, 1 for each user, which maxed out the CPU.

        Windows Server 2008 R2.
        PhantomPDF version 9.1.0.5096

        Comment


        • #5
          I just installed Foxit Reader 9.1.0.5096 on a terminal server last night and this is happening to me now too. FoxitProxyServer_Socket_RD.exe using about 50% CPU. This is on Server 2016. There is one of these processes running under each user account. As soon as I end one, the process from another user picks up.

          What is this process and what are the side effects of ending it?

          Thanks.

          Comment


          • #6
            proxima pialld Sorry for the trouble. The process is related to Foxit Creator. Did you use the software to create pdf files and is the issue replicable? Do you still get the issue after restarting the work station? If yes, please help to collect the logs and send it to us with below steps.
            1 Enable log generation by changing the value of key 'EnableLog' to 1. You could find the key under Registry Editor HKEY_CURRENT_USER\Software\Foxit Software\Foxit PDF Creator.
            2 Please reproduce your workflow which replicate the issue and send us the logs under C:\Users\'profile name'\AppData\Roaming\Foxit Software\Foxit PDF Creator\Creator-Log

            Comment


            • #7
              The user has reported the issue is persisting, even after removal and reinstallation of the product, and restart of the workstation.
              I will enable the log and send it when it has generated sufficient data.

              Comment


              • #8
                I cannot upload the log, i do not have permissions to add attachments.

                level time ThreadID content
                Debug 2018/05/30-10:13:26-152 3016 wWinMain
                Debug 2018/05/30-10:13:26-152 3016 StartTcpServer--Start : 3016
                Debug 2018/05/30-10:13:26-152 12556 AcceptThread--Start : 12556
                Debug 2018/05/30-10:13:26-651 10368 ConnectThread--Start : 10368
                Debug 2018/05/30-10:13:26-651 10368 StartReciveData--Start : 10368
                Debug 2018/05/30-10:13:26-682 10368 ExcuteProxyGetAppEdition--Start : 10368
                Debug 2018/05/30-10:13:26-682 10368 CProxyServer:roxyGetAppEdition: appType:2
                Debug 2018/05/30-10:13:26-682 10368 CProxyServer:roxyGetAppEdition: app_Reader
                Debug 2018/05/30-10:13:26-682 10368 CProxyServer:roxyGetAppEdition: edition_Reader
                Debug 2018/05/30-10:13:26-682 10368 ExcuteProxyGetAppEdition--End : 10368
                Debug 2018/05/30-10:13:26-682 10368 ExcuteProxyGetAppEdition--Start : 10368
                Debug 2018/05/30-10:13:26-682 10368 CProxyServer:roxyGetAppEdition: appType:2
                Debug 2018/05/30-10:13:26-682 10368 CProxyServer:roxyGetAppEdition: app_Reader
                Debug 2018/05/30-10:13:26-682 10368 CProxyServer:roxyGetAppEdition: edition_Reader
                Debug 2018/05/30-10:13:26-682 10368 ExcuteProxyGetAppEdition--End : 10368
                Debug 2018/05/30-10:13:26-698 10368 StartReciveData--End : 10368
                Debug 2018/05/30-10:13:26-698 10368 ConnectThread--End : 10368
                Debug 2018/05/30-10:13:26-714 12556 AcceptAInvalidSocket : 12556
                Debug 2018/05/30-10:13:26-714 12556 EndAcceptThread--End : 12556
                Debug 2018/05/30-10:13:26-714 3016 StartTcpServer--End : 3016

                Comment


                • #9
                  Originally posted by Doris Wang View Post
                  proxima pialld Sorry for the trouble. The process is related to Foxit Creator. Did you use the software to create pdf files and is the issue replicable? Do you still get the issue after restarting the work station? If yes, please help to collect the logs and send it to us with below steps.
                  1 Enable log generation by changing the value of key 'EnableLog' to 1. You could find the key under Registry Editor HKEY_CURRENT_USER\Software\Foxit Software\Foxit PDF Creator.
                  2 Please reproduce your workflow which replicate the issue and send us the logs under C:\Users\'profile name'\AppData\Roaming\Foxit Software\Foxit PDF Creator\Creator-Log
                  Is there any update on this? We support a company that uses foxit and this has appeared on several machines and frozen it. So far I can give you these details.

                  Faulting application name: FoxitProxyServer_Socket_PH.exe, version: 0.3.1.0, time stamp: 0x5ad494ae

                  Faulting module name: FXCrypto32.dll, version: 1.0.0.1225, time stamp: 0x5683bdbb

                  Exception code: 0xc0000005

                  Fault offset: 0x00010741

                  Faulting process id: 0x1b8c

                  Faulting application start time: 0x01d3f98267cecd21

                  Faulting application path: C:\Program Files (x86)\Foxit Software\Foxit PhantomPDF\Plugins\Creator\FoxitProxyServer_Socket _PH.exe

                  Faulting module path: C:\Program Files (x86)\Foxit Software\Foxit PhantomPDF\plugins\FXCrypto32.dll

                  Report Id: a7bce29e-6575-11e8-a373-3417eba7b526

                  I also have similar faults involving C:\windows\syswow64\ntdll.dll

                  It would be great if you could advise us on what to do.

                  SO far, we have been killing the process and then the system seems to be fine, but obviously the software is needed for a reason, so is there a fix for it in the pipeline?

                  Comment


                  • #10
                    DerekB Our developer has just compiled a beta version focusing on fixing the issue. Could you please download the Beta version from http://sync-us.foxitsoftware.com/iss...9.1.0.5096.exe and install it to have a try? For the log, please help to email to support@foxitsoftware.com.

                    Comment


                    • #11
                      Originally posted by aaron.mathias View Post

                      Is there any update on this? We support a company that uses foxit and this has appeared on several machines and frozen it. So far I can give you these details.

                      Faulting application name: FoxitProxyServer_Socket_PH.exe, version: 0.3.1.0, time stamp: 0x5ad494ae

                      Faulting module name: FXCrypto32.dll, version: 1.0.0.1225, time stamp: 0x5683bdbb

                      Exception code: 0xc0000005

                      Fault offset: 0x00010741

                      Faulting process id: 0x1b8c

                      Faulting application start time: 0x01d3f98267cecd21

                      Faulting application path: C:\Program Files (x86)\Foxit Software\Foxit PhantomPDF\Plugins\Creator\FoxitProxyServer_Socket _PH.exe

                      Faulting module path: C:\Program Files (x86)\Foxit Software\Foxit PhantomPDF\plugins\FXCrypto32.dll

                      Report Id: a7bce29e-6575-11e8-a373-3417eba7b526

                      I also have similar faults involving C:\windows\syswow64\ntdll.dll

                      It would be great if you could advise us on what to do.

                      SO far, we have been killing the process and then the system seems to be fine, but obviously the software is needed for a reason, so is there a fix for it in the pipeline?
                      Please share the new bug fixed build to the customer to see if the issue is gone. The download link can be found below.
                      http://sync-us.foxitsoftware.com/pm/...9.1.0.5096.msi

                      Comment


                      • #12
                        Originally posted by Doris Wang View Post

                        Please share the new bug fixed build to the customer to see if the issue is gone. The download link can be found below.
                        http://sync-us.foxitsoftware.com/pm/...9.1.0.5096.msi
                        Hi Doris,

                        I need MSI's for both as I need to deploy each to about 200 users.

                        Comment


                        • #13
                          Has something changed in the version you posted a link to above? I'm currently running that version. I'm still waiting for a permanent fix.

                          Thanks,
                          John

                          Comment


                          • #14
                            Originally posted by pialld View Post
                            Has something changed in the version you posted a link to above? I'm currently running that version. I'm still waiting for a permanent fix.

                            Thanks,
                            John
                            We have not released the upgrade yet, the link sent by doris was a workaround for users. Do you mean you have tried the link sent by doris and it still not works?

                            Comment


                            • #15
                              After v9.1.0.5096 crashed my PC (Win 7 x64) when opening 2 pdf documents (in 2 tabs) I downgraded to Version: 8.3.2.25013. BTW - It happened when I had Microsoft Word 2007 opened.
                              Edit: The Downgrading workaround seems to fix this issue.
                              Last edited by soul25; 06-12-2018, 07:33 PM.

                              Comment

                              Working...
                              X