None
closed
nobody
None
2018-07-16
2018-07-14
LehelB
No

I have a problem with recoll 1.24.1 crashing on macOS 10.13.6. This is my own build because the macports version still depends on Qt4 and I've already migrated my other Qt apps to Qt5 (because of retina display support among others). But the deps are from macports (otool output attached).

The crash happens when a file chooser dialog is opened - for example the "Add index" on the "External Indexes" tab, or the "Database directory name" on the "Global Parameters" tab. I've traced it to myGetFileName in main.cpp, then the dialog.exec call, which reaches platformHelper->exec (http://code.qt.io/cgit/qt/qtbase.git/tree/src/widgets/dialogs/qdialog.cpp#n542) where it crashes on another thread with what looks like a double free error.

Sometimes I get to the file open dialog, and the crash happens when I try to open a directory there.

I honestly don't know if this is a bug in recoll, Qt, or the native FinderKit library, but none of the other Qt apps I'm using does this when I try to open a file.

Discussion

  • medoc
    medoc
    2018-07-15

    Hi,

    Unfortunately, I have no macos machine around to reproduce this.

    I tried to run recoll with valgrind and the AddressSanitizer and MALLOC_CHECK_=1 under Linux, with no success, the tools don't seem to seen anything wrong. Using Qt 5.5.1 under ubuntu Xenial.

    I guess that the only approach I can think of would be to try and run with whatever diagnostic tools are available on the Mac, in the hope that one will be able to pinpoint the issue.

    Also, maybe try another Qt version. By the way, I don't know if this is normal or not, but you have a mix of 5.9 and 5.10 libs in the list.

     
    Last edit: medoc 2018-07-15
  • LehelB
    LehelB
    2018-07-15

    Hello,

    I've noticed the library version discrepancy myself, for some reason qt5-qtwebkit is still 5.9 in macports. I didn't give too much importance to it as QDialog is in Qt base.

    What I did now is to run recoll under Instruments with allocation tracing. No problems found, and the app doesn't crash. No only that, but since then it doesn't crash when run on its own either (even after rebooting). It's quite surprising. I don't know what Instruments did (changed the system's malloc behavior, reset some cache?), but the issue disappeared.

    In light of this, the ticket can be closed.

     
  • medoc
    medoc
    2018-07-16

    Yes, this is weird. Closing the issue, and hoping that the problem won't come back !

     
  • medoc
    medoc
    2018-07-16

    • status: open --> closed
    • milestone: -->
     

Cancel   Add attachment