Opened 10 years ago

Last modified 2 years ago

#3080 assigned bug

PhotoGrabber cannot be killed when camera is attached

Reported by: nutela Owned by: nobody
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

  • how to reproduce

unpack Photograbber from Haikuware.com, the bin should be from 28 Aug 2008, have a camera (in this case Canon Ixus) attached to USB and start Photograbber and set it up to look for a camera (see settings)

  • experienced behavior

Photograbber never updates its window, cannot be killed with ctrl-alt-del or kill -9, the window leaves an area on the desktop which is wrongly redrawn, after several kill -9 of PhotoGrabber's threads, the picasso thread is hogging cpu. only when the camera is switched off the Deskbar entry disapeared, the area on the desktop previously occupied by PhotoGrabber is being redrawn normally again.

  • expected behavior

Every app should be killed by ctrl-alt-del or always with kill -9, picasso shouldn't get confused? :-)

Attachments (1)

photograbber.prefs (168 bytes) - added by nutela 10 years ago.
Photograbber preferences

Download all attachments as: .zip

Change History (6)

Changed 10 years ago by nutela

Attachment: photograbber.prefs added

Photograbber preferences

comment:1 Changed 10 years ago by nutela

Regarding the App_server's picasso thread; what I wrote above is not true, even after killing PhotoGrabber, the 'window-space' is not deleted, the area which Photograbber covered is still drawn over the desktop, how could I debug it when it is still running?

comment:2 Changed 4 years ago by vidrep

Shouldn't this be in Haikuports?

comment:3 Changed 4 years ago by waddlesplash

No, because kill -9 should kill things no matter what they're doing or blocked on.

comment:4 Changed 4 years ago by pulkomandy

This happens because the app is locked inside a system call. Possibly inside the USB stack, but attaching Debugger to it and extracting a report (backtrace of all threads) would be helpful.

comment:5 Changed 2 years ago by axeld

Owner: changed from axeld to nobody
Status: newassigned
Note: See TracTickets for help on using tickets.