[BUG REPORT] UP 1.4 (for mac) crashes after print cmd issued

Support for UP Plus and UP Plus 2. To report a bug, post with a title [BUG REPORT]. To request a feature, post with a title [FEATURE REQUEST]
Post Reply
markfarnell
Posts: 2
Joined: Mon Feb 04, 2013 5:45 am

[BUG REPORT] UP 1.4 (for mac) crashes after print cmd issued

Post by markfarnell » Mon Feb 04, 2013 5:57 am

I am using an aluminium MacBook late 2008 (Macbook 5,1) with OS X 10.8.2 installed. When I run UP 1.4, here is the console screen:

laptop:MacOS abc$ ./UP
2013-02-04 18:27:01.873 UP[3937:707] Could not connect the action TestUSB: to target of class MacUPView
Found device VID 0x4745 (18245), PID 0x0001 (1), release 256
Configuration value is 1
2 endpoints found
Endpoint 1: Bulk In 1, max packet 64, interval 0
Endpoint 2: Bulk Out 1, max packet 64, interval 0
2013-02-04 18:27:02.079 UP[3937:707] Temp Dir: /Library/Caches
2013-02-04 18:32:57.930 UP[3937:707] Set Print Setup parametrs
2013-02-04 18:32:57.931 UP[3937:707] Panel is <PrintSetupPanel: 0x59e130>
2013-02-04 18:33:43.992 UP[3937:707] Begin Print model
2013-02-04 18:33:44.025 UP[3937:9823] Begin Print Thread
2013-02-04 18:33:44.025 UP[3937:9737] Begin progress tread
2013-02-04 18:34:10.562 UP[3937:9737] End Slice, Beging Send Data
2013-02-04 18:35:31.290 UP[3937:9737] End progress thread
2013-02-04 18:35:32.329 UP[3937:9823] NSAlert is being used from a background thread, which is not safe. This is probably going to crash sometimes. Break on void _NSAlertWarnUnsafeBackgroundThreadUsage() to debug. This will be logged only once. This may break in the future.
2013-02-04 18:35:40.832 UP[3937:9823] End Print Thread


Sometimes, when I click the OK button of the print dialogue and after (?) it loads the data to the printer, one of the pthread crashes. From my memory, it say something about "floating point exception" This only occurs sometime, which leads me to think this may be some form of data race issues, especially after seeing the above message.

I can't include the backtrace, because the current run, I can't reproduce the crash. Since the crash occurs only sometimes and pthread is used, this makes me think that perhaps there may be data race.

Could you please have a look?

Thanks!

Mark

Post Reply