I have a single user that is reporting a consistent crash in a contract-application when trying to print. He says the crash occurs immediately when he clicks the "Print" button in one of my project's windows that then calls
g = OpenPrinterDialog( ps, ow )
where ps is a PrinterSetup object and ow is the window in question.
The user says the printer dialog is never shown. The application immediately crashes. They sent me the a crash report, which narrows the crash down to the following:
Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000008c Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler  VM Regions Near 0x8c: --> __TEXT 0000000000001000-0000000000b35000 [ 11.2M] r-x/rwx SM=COW /Applications/REDACTED.app/Contents/MacOS/REDACTED Application Specific Information: Performing @selector(performClick:) from sender XOJButton 0x16c19060 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.print.framework.PrintCore0x936c8717 PJCSessionHasApplicationSetPrinter + 6 1 com.apple.print.framework.Print.Private0x061ba9c2 0x61a2000 + 100802 2 com.apple.AppKit 0x925e6aee -[NSWindowController _windowDidLoad] + 671 3 com.apple.AppKit 0x92588e62 -[NSWindowController window] + 115 4 com.apple.AppKit 0x9280df2e -[NSPrintPanel beginSheetWithPrintInfo:modalForWindow:delegate:didEndSelector:contextInfo:] + 504 5 com.xojo.XojoFramework 0x00e687af 0xe4d000 + 112559 6 com.xojo.XojoFramework 0x00fb5e99 RuntimeOpenPrinterDialog + 212 7 com.searchwaresolutions.REDACTED0x00147e47 REALbasic.OpenPrinterDialog%o<Graphics>%o<PrinterSetup>o<Window> + 79
I cut the crash report off at what I recognized as the OpenPrinterDialog call and redacted the application name as it is a private and confidential application for my user.
Other users using the same build of the application are not seeing the crash. This user says that the crash only occurs when logged in as a non-Administrator user. When logged in as an Administrator, everything works fine. I do not have access to the specific computer in question and can only go by what the user translates for me.
I have asked the user to try printing to a different printer, but have not yet heard back. In the meantime, does this ring a bell for anyone? I'm sure it its something specific to this particular computer (and even the account on that computer), but I'm looking for something more concrete to help them figure out where to look to correct.
If not, I understand, but I figure it couldn't hurt to try.