Re: Multi-threaded opengl or view access crashes system?
Re: Multi-threaded opengl or view access crashes system?
- Subject: Re: Multi-threaded opengl or view access crashes system?
- From: Theo Vosse <email@hidden>
- Date: Fri, 21 Oct 2005 12:47:39 +0200
Are you taking into consideration the things you learned from the
thread on "setFrame blocks thread"?
That was another window, but yes, this window already prohibited
drawRect calls. It runs an animation (of a neural network) in a
background thread and drawing is done only there. Of course, that
might be the problem if resizing doesn't do normal setNeedsDisplay/
drawRect calls, and I should leave all drawing to the main thread,
just posting notifications.
Also, are you absolutely sure that you adhere to other thread
safety rules? Check the docs for every single method you call from
non-main threads!
Yes, the application never blocked before. I've even got menu items
to debug this process by locking/unlocking at will and so far not a
single error, not even on my other machine, which has dual
processors. I follow really simple rules: drawContent takes the lock
and unlocks after drawing, and content altering functions do the same.
That said, nothing you do in an user space application should of
course be able to trigger a system wide crash / hang. If you can
reproduce the problem, make sure to file a bug report!
I'm afraid the reproduction will be tricky and nothing I'm interested
in provoking. Perhaps I should set up another system with a remote
login to see what's happening. It might be that only the window
manager is hanging.
Theo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden