[Okular-devel] [Bug 253284] New: okular crashes on Windows 7 Pro 64-bit upon File > Open

[Rand Kmiec]

https://bugs.kde.org/show_bug.cgi?id=253284

           Summary: okular crashes on Windows 7 Pro 64-bit upon File >
                    Open
           Product: okular
           Version: 0.10.4
          Platform: MS Windows
        OS/Version: MS Windows
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: okular-devel at kde.org
        ReportedBy: rkdart at alum.dartmouth.org


Version:           0.10.4 (using KDE 4.4.4) 
OS:                MS Windows

Using Windows 7 (professional, 64-bit), okular crashes when I choose File >
Open.  No open dialog actually comes up, just get an "okular.exe has stopped
working" window with a crash in QtCore4.dll.  Same behavior occurs whether or
not I run in administrative mode.  Other Qt-based apps such as Qt Creator do
not crash when I try their File > Open dialogs.  

Looking at Process Monitor, it looks like okular does go through my drives and
tries to list contents, failing to do so on two USB drives that host TrueCrypt
volumes and thus can't be accessed directly (D: and F:, which are mounted as P:
and Q:), with result "INVALID PARAMETER".  I'm suspicious that this is the
reason for the crash.

  Disabling access to those 2 drives via
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoDrives
and
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoViewOnDrive
prevents them from showing up in the Computer display, but they are still
scanned according to Process Monitor, with the "INVALID PARAMTER" message.

Reproducible: Always

Steps to Reproduce:
Choose File > Open

Actual Results:  
okular crashes

Expected Results:  
File open dialog should be displayed

OS: WindowsNT (i686) release Windows 7
Compiler: cl.exe

Crash data:
Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    okular.exe
  Application Version:    0.0.0.0
  Application Timestamp:    4c0dbfc4
  Fault Module Name:    QtCore4.dll
  Fault Module Version:    4.6.2.0
  Fault Module Timestamp:    4c0a29a7
  Exception Code:    c0000005
  Exception Offset:    001009b3
  OS Version:    6.1.7600.2.0.0.256.48
  Locale ID:    1033
  Additional Information 1:    0a9e
  Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:    0a9e
  Additional Information 4:    0a9e372d3b4ad19135b953a78882e789

In case the call stack is useful (probably isn't), here's what I get from
Visual Studio:
==========================================

     QtCore4.dll!671009b3()     
     [Frames below may be incorrect and/or missing, no symbols loaded for
QtCore4.dll]    
     QtGui4.dll!652dcca5()     
     QtGui4.dll!65446e4f()     
     QtGui4.dll!652e3cf1()     
     kio.dll!0176bc1a()     
     kio.dll!0176c85a()     
     kfile.dll!08cd3ca3()     
    msvcr90.dll!free(void * pBlock=0x08d0e8b5)  Line 110    C
     00dad33c()    
     kernel32.dll!_HeapFree at 12()  + 0x14 bytes

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.