Announcement

Collapse
No announcement yet.

Foxit Reader (Linux) Crashes on Save

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

  • crash Foxit Reader (Linux) Crashes on Save

    Hi,

    first of all I really like the new version of Foxit Reader for Linux. I'm currently using it on a daily basis and make heavy use of the commenting functions, where Foxit Reader really shines.
    Unfortunately I'm currently hitting a bug when saving a commented PDF.

    What I'm I doing:
    1. opening the PDF
    2. adding Comments
    3. adding Text Comment
    4. Not leaving the Input field (would be still able to type text)
    5. Pressing STRG+S (save)
    6. Foxit Crashes

    What is supposed to happen:
    1. Saving the document

    What does actually happen
    1. Foxit saves a temporary file
    2. Foxit crashes

    Additional info:
    1. currently this only happens when still inside a text comment (via "add line of text"), other functions seem to be unaffected
    2. version info:
    • Foxit Version: 1.1.0.0225
    • OS: up2date Archlinux x64
    • QT Installer Framework: 2.0.1
    • QT version: 5.4.2

    3. console log when the bug happens:
    Code:
    [TimeStamp]-----CReader_DocumentEx::Save-----begin
    QObject::connect: No such slot CMainWindow::Slot_ShowSaveAsDialogWhenSaveFailed(Q String)
    QObject::connect: (receiver name: 'mainwindow')
    QObject::connect: No such slot CMainWindow::Slot_UpdatePermissions()
    QObject::connect: (receiver name: 'mainwindow')
    QObject::killTimer: Timers cannot be stopped from another thread
    QObject::~QObject: Timers cannot be stopped from another thread
    richtext:
    "<?xml version="1.0"?><body xmlns="http://www.w3.org/1999/xhtml" xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/" xfa:APIVersion="Acrobat:11.0.0" xfa:spec="2.0.2"><p dir="ltr"><span style="text-align:left;font-size:10pt;font-style:normal;font-weight:normal;color:#000000;font-family:Ubuntu">test</span></p></body>"
    CBA_Annot::SetRect:579.186890 109.198936 597.276917 120.408936
    
    FRDocOnChange
    progressbar---create----frd_docex.cpp
    Slot_CreateProgressBar
    libpng warning: iCCP: known incorrect sRGB profile
    libpng warning: iCCP: known incorrect sRGB profile
    libpng warning: iCCP: known incorrect sRGB profile
    Speicherzugriffsfehler (Speicherabzug geschrieben)
    fuser
    Last edited by fuser; 04-07-2016, 09:07 AM.

  • #2
    Dear fuser,

    I apologize for any hassle and inconvenience this may cause for you.Regarding this crash issue you referred,we still need your help to send us the following information for further diagnosis:
    1:The detailed version number of your Archlinux OS.
    2: Did this issue happen to all or just some specific PDF files when you try to those procedures that you mentioned in this thread?Please send us one PDF file sample.
    3:Which tools that you have chosen for "adding comments" and "adding Text Comment" that you referred in step2 and step3.
    4:Are you able to replicate this crash issue again or it is just an occasional issue?
    5:Please help to go to "Help"menu in Foxit Reader>"About Foxit Reader"to open the about dialog box there,please double click on the word "Foxit"there three times ,then should be a new pop-up window appear in which you are able to set Foxit output log path.
    Please set log path there and click"OK",restart your Foxit Reader to make the settings to take effect.
    Please help to send us the send the log file for us after you having reproduced the crash issue again.

    Comment


    • #3
      Lisa_lee

      1. Archlinux is a rolling release distribution, meaning there is no such thing like a version of the os (like for example Ubuntu 14.04 LTS). In contrast a new version of a software is available when considered stable. I could however provide you with all library versions you need. From the package manager i could determine the following dependencies: desktop-file-utils 0.22-1, p7zip 9.38.1-4, qt5-tools 5.6.0-2, qt-installer-framework 2.0.1-3. Please tell me If you need additional Information.

      2. It happened on all PDFs. I could not add an example of the temporary (I suppose) save file, the upload failed. It was named "~$Example.pdf" and was empty (checked with "less" and "cat" on the console)

      3. I used the typewriter tool from "Comments"

      4. It is reproducible every time I try to save a PDF, IF I did not leave the Typewriter feature before (by clicking anywhere or pressing ESC). My current workaround is pressing ESC before saving the document. Every time, which slows me down a bit during lectures where I need to type in comments fast (which apart from the bug works great by the way).

      5. If i press ok on the second dialog to set my log path I get the following error: "open /usr/lib/foxitreader/config.xml fail!". I can however open the file via "cat /usr/lib/foxitreader/config.xml":
      Code:
      <?xml version="1.0" encoding="UTF-8"?>
      <Log>
      <Name>Foxit Reader Startup Log</Name>
      <Startup>false</Startup>
      <ShowTraiExpDlg>true</ShowTraiExpDlg>
      </Log>
      The log file however is not created. therefore I attached the console output ("foxit.txt") of foxitreader from the start until the crash.

      I hope this helps. If you need additional information like a strace output or something like this, I would happily provide it.


      fuser


      EDIT: apparently I cannot post in this thread anymore, here is a link to a syslog coredump when the crash happens: http://pastebin.com/30g1LMVQ
      Attached Files
      Last edited by fuser; 04-20-2016, 03:36 PM.

      Comment


      • #4
        Dear fuser,

        Thanks for your reply.This issue"Foxit Reader (Linux) Crashes when save a commented PDF file without leaving the Input field"has been submitted to our internal bug tracking system for our QA team to do further analysis with report ID#0076458.
        I will keep you posted for any updates about this issue.

        Comment


        • #5
          Lisa_lee

          if it's of any help, please find below (attaching did not work this time) the syslog coredump when foxit crashes.

          Code:
          Process 1917 (foxitreader) of user 1000 dumped core.
          
          Stack trace of thread 1917:
          #0  0x00007fb6bfa494a0 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
          #1  0x00007fb6bfa9db8e _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5)
          #2  0x00007fb6bfa9e0b1 n/a (libQt5Core.so.5)
          #3  0x00007fb6be1e6f07 g_main_context_dispatch (libglib-2.0.so.0)
          #4  0x00007fb6be1e7160 n/a (libglib-2.0.so.0)
          #5  0x00007fb6be1e720c g_main_context_iteration (libglib-2.0.so.0)
          #6  0x00007fb6bfa9ec8f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
          #7  0x00007fb6bfa476fa _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
          #8  0x00007fb6c0f0d53c _ZN7QDialog4execEv (libQt5Widgets.so.5)
          #9  0x000000000052cd89 n/a (FoxitReader)
          #10 0x000000000044965b n/a (FoxitReader)
          #11 0x000000000053e5a8 n/a (FoxitReader)
          #12 0x00007fb6bfa76659 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5)
          #13 0x00007fb6c0d58c4b _ZN7QWidget5eventEP6QEvent (libQt5Widgets.so.5)
          #14 0x00007fb6c0e6b0db _ZN11QMainWindow5eventEP6QEvent (libQt5Widgets.so.5)
          #15 0x00007fb6c0d1468c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5)
          #16 0x00007fb6c0d198f6 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5)
          #17 0x00007fb6bfa49518 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
          #18 0x00007fb6bfa4b3da _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5)
          #19 0x00007fb6bfa9e883 n/a (libQt5Core.so.5)
          #20 0x00007fb6be1e6f07 g_main_context_dispatch (libglib-2.0.so.0)
          #21 0x00007fb6be1e7160 n/a (libglib-2.0.so.0)
          #22 0x00007fb6be1e720c g_main_context_iteration (libglib-2.0.so.0)
          #23 0x00007fb6bfa9ec8f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
          #24 0x00007fb6bfa476fa _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
          #25 0x0000000000478ad4 n/a (FoxitReader)
          #26 0x000000000047656a n/a (FoxitReader)
          #27 0x0000000000446551 n/a (FoxitReader)
          #28 0x000000000053ea0e n/a (FoxitReader)
          #29 0x00007fb6bfa75870 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
          #30 0x00007fb6c0d0b3d2 _ZN7QAction9triggeredEb (libQt5Widgets.so.5)
          #31 0x00007fb6c0d0def0 _ZN7QAction8activateENS_11ActionEventE (libQt5Widgets.so.5)
          #32 0x00007fb6c0d0e84f _ZN7QAction5eventEP6QEvent (libQt5Widgets.so.5)
          #33 0x00007fb6c0d1468c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5)
          #34 0x00007fb6c0d198f6 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5)
          #35 0x00007fb6bfa49518 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
          #36 0x00007fb6bffbe826 _ZN12QShortcutMap13dispatchEventEP9QKeyEvent (libQt5Gui.so.5)
          #37 0x00007fb6bffbe8d9 _ZN12QShortcutMap11tryShortcutEP9QKeyEvent (libQt5Gui.so.5)
          #38 0x00007fb6bff77716 _ZN22QWindowSystemInterface19handleShortcutEventEP7QWindowmi6QFlagsIN2Qt16KeyboardModifierEEjjjRK7QStringbt (libQt5Gu
          #39 0x00007fb6bff8fa14 _ZN22QGuiApplicationPrivate15processKeyEventEPN29QWindowSystemInterfacePrivate8KeyEventE (libQt5Gui.so.5)
          #40 0x00007fb6bff94b65 _ZN22QGuiApplicationPrivate24processWindowSystemEventEPN29QWindowSystemInterfacePrivate17WindowSystemEventE (libQt5Gu
          #41 0x00007fb6bff71d6b _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5)
          #42 0x00007fb6b5b9fd10 n/a (libQt5XcbQpa.so.5)
          #43 0x00007fb6be1e6f07 g_main_context_dispatch (libglib-2.0.so.0)
          #44 0x00007fb6be1e7160 n/a (libglib-2.0.so.0)
          #45 0x00007fb6be1e720c g_main_context_iteration (libglib-2.0.so.0)
          #46 0x00007fb6bfa9ec8f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
          #47 0x00007fb6bfa476fa _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
          #48 0x00007fb6bfa4fb7c _ZN16QCoreApplication4execEv (libQt5Core.so.5)
          #49 0x000000000043ee2e n/a (FoxitReader)
          #50 0x00007fb6be71f710 __libc_start_main (libc.so.6)
          #51 0x000000000043e257 n/a (FoxitReader)
          
          Stack trace of thread 1918:
          #0  0x00007fb6be7ddc3d poll (libc.so.6)
          #1  0x00007fb6b9f37ae2 n/a (libxcb.so.1)
          #2  0x00007fb6b9f39757 xcb_wait_for_event (libxcb.so.1)
          #3  0x00007fb6b5b6ba99 n/a (libQt5XcbQpa.so.5)
          #4  0x00007fb6bf875de8 n/a (libQt5Core.so.5)
          #5  0x00007fb6bf344424 start_thread (libpthread.so.0)
          #6  0x00007fb6be7e6cbd __clone (libc.so.6)
          
          Stack trace of thread 3969:
          #0  0x00007fb6bf34d77d __nanosleep (libpthread.so.0)
          #1  0x00007fb6bf92208d n/a (libQt5Core.so.5)
          #2  0x00007fb6bf8751bb _ZN7QThread5sleepEm (libQt5Core.so.5)
          #3  0x0000000000480c42 n/a (FoxitReader)
          #4  0x00000000004807f1 n/a (FoxitReader)
          #5  0x00007fb6bf875de8 n/a (libQt5Core.so.5)
          #6  0x00007fb6bf344424 start_thread (libpthread.so.0)
          #7  0x00007fb6be7e6cbd __clone (libc.so.6)
          
          Stack trace of thread 1919:
          #0  0x00007fb6be7ddc3d poll (libc.so.6)
          #1  0x00007fb6be1e70fc n/a (libglib-2.0.so.0)
          #2  0x00007fb6be1e720c g_main_context_iteration (libglib-2.0.so.0)
          #3  0x00007fb6bfa9ec8f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
          #4  0x00007fb6bfa476fa _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
          #5  0x00007fb6bf870fe4 _ZN7QThread4execEv (libQt5Core.so.5)
          #6  0x00007fb6b3fcea55 n/a (libQt5DBus.so.5)
          #7  0x00007fb6bf875de8 n/a (libQt5Core.so.5)
          #8  0x00007fb6bf344424 start_thread (libpthread.so.0)
          #9  0x00007fb6be7e6cbd __clone (libc.so.6)

          Comment


          • #6
            Lisa_lee

            if it's of any help, please find below (attaching did not work this time) a syslog coredump when foxit crashes.

            http://pastebin.com/30g1LMVQ

            Comment


            • #7
              Any updates on this? I can confirm this bug exists on the latest 1.1.0.0225 on RHEL/CentOS 7. Workaround is to avoid using "Save" and use "Save As" (to a new filename) instead.

              Comment


              • #8
                kz26 fuser


                I have forwarded your info to our team, and remind them to fix the issue as soon as possible.
                You may email to support@foxitsoftware.com with this ID# to track the processing status or post here. Thank you.

                Comment

                Working...
                X