You are viewing limited content. For full access, please sign in.

Question

Question

lf crashing when viewing document at certain page

asked on May 2, 2017

My client is running into an issue where when they open a specific document and scroll to the thumbnail for page 44 in the document, the whole client freezes then crashes and the user has to open LF all over again. They say it's happening to multiple users, but only this 1 document. Here are the event log entries when the application crashes:

"Application Error":

Faulting application name: LF.exe, version: 10.2.0.839, time stamp: 0x5876f4ad
Faulting module name: LFSO102.dll, version: 10.2.0.383, time stamp: 0x5862fabe
Exception code: 0xc0000005
Fault offset: 0x001fcf46
Faulting process id: 0x1334
Faulting application start time: 0x01d2c2a97ce92009
Faulting application path: C:\Program Files (x86)\Laserfiche\Client\LF.exe
Faulting module path: C:\Program Files (x86)\Common Files\Laserfiche\10.2\LFSO102.dll
Report Id: 21c2b149-2e9d-11e7-ae41-a86bada68f9c

 

".NET Runtime":

Application: LF.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 646ECF46

 

They are on LF 10.2.0.839, and Windows 7 Pro SP1.

If anyone knows what these errors mean, I'd appreciate the insight. Thanks!

0 0

Replies

replied on May 2, 2017

Hi Ricardo,

Is it possible to provide a briefcase containing the document in question to support? There might be something specific to how that document exists in the system. 

0 0
replied on May 3, 2017

Please open a support case request.

When opening the support cases, please:

  • Mention the URL to this Laserfiche Answers post.
  • If possible, please provide a briefcase containing the document in question.

 

Even if the customer does not allow access to the document, it is recommended to open a support case anyway. Our support team will be able to guide you through many different ways of investigating the issue.

Here are some examples of ways of investigating the issue without direct access to the document.

  • Discuss with the customer whether it is acceptable to capture a "crash dump" from the application.
    • A crash dump is typically necessary when troubleshooting application crashes.
    • Note that a "crash dump" may contain parts of the image file causing the problem, along with any other data that might be in application memory.
  • Try to narrow down the problem. Some examples:
    • Does the problem still occur when the preceding document pages (those that aren't causing the problem) are deleted?
    • Does the problem still occur when the annotations on the problem-causing page are deleted? If the problem stops happening once the annotations are deleted, the problem might be caused by the annotations rather than the image or thumbnail.
    • Does the problem still occur when the text on the page are deleted?
  • Try to access the image files stored on the volume using a third-party image viewer application.
  • Enable LFSO tracing. The tracing log may indicate the sequence of operations that immediately precedes the crash.
  • Use SDK / Scripting (such as Laserfiche Workflow Scripting) to access the document, and see if any error occurs.

 

Thank you.
 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.