Pdfpenpro 9 crashes when selecting print

#PDFPENPRO 9 CRASHES WHEN SELECTING PRINT PDF#
#PDFPENPRO 9 CRASHES WHEN SELECTING PRINT INSTALL#
#PDFPENPRO 9 CRASHES WHEN SELECTING PRINT DRIVERS#
#PDFPENPRO 9 CRASHES WHEN SELECTING PRINT UPDATE#
#PDFPENPRO 9 CRASHES WHEN SELECTING PRINT SOFTWARE#

Install a custom termination handler using std::set_terminate You can improve your exception handling code and if this is a production application, you should:ДЄ. WinDbg for this, details about the avaiable post-mortem debuggers and their installation at MSDN If the previous solution doesn't work, you need to catch the unhandled exception and attach a post-mortem debugger the instance the crash occurs. That might make the crash reproducible with the debugger attached. You can specify this either in your computer properties, or in the Project Settings in Visual Studio. You can turn the debug heap off by using environment variable _NO_DEBUG_HEAP.

In short, at least the Visual Studio Debugger uses the Debug Heap automatically when attached to a program. The presence of a debugger may change the behavior of a program too, both for release and debug builds. Each of these differences might cause a bug in the Release build that doesn't exist in the Debug build. Release and Debug builds behave differently for many reasons. No answer so far has tried to give a serious overview about the available techniques for debugging release applications: Thanks everybody for your help in finding this problem! Does anyone have any advice as to how I could get some more meaningful information here and hopefully fix this bug?Д®dit: The problem was indeed caused by an out-of-bounds array, which I describe more in this post.

It would be really nice if I could get Windows to print out a stack trace, or something other than simply terminating the program as if it had exited cleanly. This is happening under Windows Vista, btw, and unfortunately I don't have access to an XP machine right now to test on. The crash only occurs when launching from the command line. Same goes when launching from WinDbg.exe. When I attempt to run this program inside of Visual Studio, it doesn't crash. Through caveman debugging (ie, nasty printf() messages all over the place), I have determined the test method where the code is crashing, though unfortunately the actual crash seems to happen in some destructor, since the last trace messages I see are in other destructors which execute cleanly. I still don't know what the precise issue was, but it SEEMED to be related to a Windows User Access permissioning for files within that Temp folder that were cleared out when I ran Disk Cleanup.I've got a 'Schroedinger's Cat' type of problem here - my program (actually the test suite for my program, but a program nonetheless) is crashing, but only when built in release mode, and only when launched from the command line. It also continued to work after the aforementioned reboots.

#PDFPENPRO 9 CRASHES WHEN SELECTING PRINT PDF#

However, immediately after clearing the Temporary Files the print to PDF issue went away.

#PDFPENPRO 9 CRASHES WHEN SELECTING PRINT UPDATE#

In my case it (seemed to ) force a Windows update that wouldn't complete until shutting the computer off during the update that was 'stuck' on 100% and subsequently booting into safe mode with networking and then rebooting again. Clearing the Temporary Files MAY cause other issues, so use caution and backup accordingly before trying this. Specifically, it was the 'Temporary Files' that needed to be cleaned up. It was the Windows 7 'Disk Cleanup' tool. (there were a NUMBER of things I tried based on those support pages before discovering the below, which I've omitted)

#PDFPENPRO 9 CRASHES WHEN SELECTING PRINT SOFTWARE#

However, that error was one that was documented on the support pages for that software and one of the possible fixes that was recommended ended up solving this issue for me. Ultimately, what put me on the right path (and there is NO NEED for others to do this) is installing a different PDF rendering software (trial version) which ALSO returned an error when attempting to render the PDF using the Print to PDF function.

#PDFPENPRO 9 CRASHES WHEN SELECTING PRINT DRIVERS#

Changing drivers for the Adobe PDF printer.

Deleting and manually installing the Adobe PDF Printer.

Uninstalling/reinstalling ScanSnap Manager software (re-installed with no issues).

uninstalling/reinstalling acrobat and then updating acrobat.

At the point in the scanning process when the PDF would usually be rendered, the ScanSnap software returned a 'Failed to communicate with the ScanSnap' error box and the PDF was not created. Additionally, in my case the print jobs were stuck in the print spooler and couldn't be cancelled and deleted from there using the options available in the print queue dialog (but they could be deleted by stopping the spooler service and manually deleting the items in the print queue).ДЄn additional symptom (that I later found was related to this issue) is that I was unable to scan to PDF using my Fujitsu ScanSnap ix500 scanner. I was experiencing similar symptoms as described by OP with the exception that I was able to close the 'Creating Adobe PDF' dialog by clicking the close button ('X') for the dialog box.

Pdfpenpro 9 crashes when selecting print