Bug 375506

Summary:	Crashing when highlighting in long document
Product:	[Applications] okular	Reporter:	thedougw
Component:	general	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	aacid, robby.engelmann, simonandric5
Priority:	NOR	Keywords:	triaged
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description thedougw 2017-01-24 16:26:43 UTC

Application: okular (0.16.2)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: WindowsNT Windows 6.2 i686

-- Information about the crash:
- What I was doing when the application crashed:

I'm using the F6 reviewing tools to highlight some text throughout a long document. I'm navigating the document by scrolling through it quickly. At some point, after a few minutes of having the document open, the PDF pages no longer display (plain white). The thumbnails still appear correct. After this, the program crashes. I am using KDE on Windows 10.

- Custom settings of the application:

Custom XML file and icons (adding more colors for highlighting) as detailed here: http://douglaswhitaker.com/2014/06/pdf-reader-for-windows-with-highlighting/

The crash can be reproduced sometimes.

-- Backtrace:
Application: Okular (okular.EXE), signal: EXCEPTION_ACCESS_VIOLATION


ntdll.dll!NtWaitForWorkViaWorkerFactory() [[unknown] @ -1] at 0x77c001cc
KERNEL32.DLL!BaseThreadInitThunk() [[unknown] @ -1] at 0x750362c4
ntdll.dll!RtlSubscribeWnfStateChangeNotification() [[unknown] @ -1] at 0x77bf0fd9
ntdll.dll!RtlSubscribeWnfStateChangeNotification() [[unknown] @ -1] at 0x77bf0fa4


MSVCR100.dll!memset() [[unknown] @ -1] at 0x4bd26df
poppler-qt4.dll!Poppler::FormFieldButton::~FormFieldButton() [[unknown] @ -1] at 0xae30072
poppler-qt4.dll!Poppler::FormFieldButton::~FormFieldButton() [[unknown] @ -1] at 0xadcab10
poppler-qt4.dll!Poppler::FormFieldButton::~FormFieldButton() [[unknown] @ -1] at 0xadcabff
poppler-qt4.dll!Poppler::FormFieldButton::~FormFieldButton() [[unknown] @ -1] at 0xadd7e1d


ntdll.dll!NtWaitForMultipleObjects() [[unknown] @ -1] at 0x77bfeb8c
KERNELBASE.dll!WaitForMultipleObjects() [[unknown] @ -1] at 0x76221a98
QtCore4.dll!QString::contains() [[unknown] @ -1] at 0x66d64313
QtCore4.dll!QThread::setTerminationEnabled() [[unknown] @ -1] at 0x66c97ddd
QtCore4.dll!QEventDispatcherWin32::`default constructor closure'() [[unknown] @ -1] at 0x66c976fd


ntdll.dll!NtRemoveIoCompletion() [[unknown] @ -1] at 0x77bfe64c
KERNEL32.DLL!BaseThreadInitThunk() [[unknown] @ -1] at 0x750362c4
ntdll.dll!RtlSubscribeWnfStateChangeNotification() [[unknown] @ -1] at 0x77bf0fd9
ntdll.dll!RtlSubscribeWnfStateChangeNotification() [[unknown] @ -1] at 0x77bf0fa4


ntdll.dll!NtWaitForWorkViaWorkerFactory() [[unknown] @ -1] at 0x77c001cc
KERNEL32.DLL!BaseThreadInitThunk() [[unknown] @ -1] at 0x750362c4
ntdll.dll!RtlSubscribeWnfStateChangeNotification() [[unknown] @ -1] at 0x77bf0fd9
ntdll.dll!RtlSubscribeWnfStateChangeNotification() [[unknown] @ -1] at 0x77bf0fa4


ntdll.dll!NtWaitForMultipleObjects() [[unknown] @ -1] at 0x77bfeb8c
KERNEL32.DLL!BaseThreadInitThunk() [[unknown] @ -1] at 0x750362c4
ntdll.dll!RtlSubscribeWnfStateChangeNotification() [[unknown] @ -1] at 0x77bf0fd9
ntdll.dll!RtlSubscribeWnfStateChangeNotification() [[unknown] @ -1] at 0x77bf0fa4


QtCore4.dll!QEventDispatcherWin32::event() [[unknown] @ -1] at 0x66da8000
QtGui4.dll!QApplicationPrivate::notify_helper() [[unknown] @ -1] at 0x642a04cd
kdeui.dll!QList<KSortableItem<QString,int> >::value() [[unknown] @ -1] at 0x3a68c10
QtCore4.dll!QObject::QObject() [[unknown] @ -1] at 0x66d9039e
QtCore4.dll!QTimer::timerEvent() [[unknown] @ -1] at 0x66d981e5
okularcore.dll!Okular::AnnotationProxy::operator=() [[unknown] @ -1] at 0x78a4fb2
ntdll.dll!RtlReAllocateHeap() [[unknown] @ -1] at 0x77bd9fae

Report to https://bugs.kde.org/

Comment 1 Robby Engelmann 2017-11-24 07:10:24 UTC

I also see a crash in okular (KDE apps 17.12 beta) running on the latest Tumbleweed snapshot.
I do not have a bugtrace because drkonqi does not start. However, it also crashes upon highlighting text in a large pdf document.

If you need more information to fix it, please let me know how to obtain them!

Comment 2 Robby Engelmann 2017-11-24 07:15:01 UTC

Bit differently from the original description (for windows), here pdf pages are always shown, but okular crashes after highlighting 4-6 text positions every time.
And I do not have any custom settings applied

Comment 3 Albert Astals Cid 2017-12-03 11:57:55 UTC

get us a backtrace otherwise there's nothing we can do

https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_with_GDB

Comment 4 Albert Astals Cid 2017-12-03 11:58:37 UTC

i'm really not sure that you're not hijacking something else, but oh well

Comment 5 Robby Engelmann 2017-12-03 12:12:50 UTC

I opened another bug report, as I thought my one is different from this one.
See https://bugs.kde.org/show_bug.cgi?id=387247

Comment 6 Andrew Crouthamel 2018-09-28 03:11:39 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 7 Andrew Crouthamel 2018-10-28 03:27:38 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!