#851 closed bug (fixed)
[GLTeapot] crash if you middle click on teapot
Reported by: | diver | Owned by: | jackburton |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Kits/Interface Kit | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
GLTeapot crash if you middle click on teapot. Tested under vmware with hrev18823. back trace will follow...
Attachments (1)
Change History (11)
by , 18 years ago
Attachment: | GLTeapot2.PNG added |
---|
follow-up: 3 comment:1 by , 18 years ago
Component: | Applications → User Interface/InterfaceKit |
---|---|
Owner: | changed from | to
I think it's a bug in BPopUpMenu::_go().
comment:2 by , 18 years ago
Milestone: | → R1 |
---|---|
Status: | new → assigned |
comment:3 by , 18 years ago
Replying to jackburton:
I think it's a bug in BPopUpMenu::_go().
Actually, I'm not so sure anymore. In this particular case, GLTeapot asks for a synchronous popup menu. Since BPopUpMenu::Go() is called from MouseDown(), the looper (window) should be locked already. So I can't see why UpdateIfNeeded() could complain...
comment:4 by , 18 years ago
Maybe it's just me, but the lines in GLTeapot's ObjectView.cpp::MouseDown() look highly suspicious:
while (Window()->IsLocked()) { locks++; Window()->Unlock(); };
Also, it calls BPopUpMenu::Go() outside of having locked the window.
follow-up: 6 comment:5 by , 18 years ago
I've fixed this problem locally by making sure BWindow::UpdateIfNeeded() locks properly. Do you mind if I commit it?
comment:6 by , 18 years ago
Replying to axeld:
I've fixed this problem locally by making sure BWindow::UpdateIfNeeded() locks properly. Do you mind if I commit it?
Go on!
follow-up: 8 comment:7 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fixed in hrev18946.
comment:8 by , 18 years ago
follow-up: 10 comment:9 by , 18 years ago
I'll look into it, but frankly, I don't think it can be caused by this: the window is locked anyway (usually) at this point, so an additional lock really shouldn't matter at all.
comment:10 by , 18 years ago
Replying to axeld:
I'll look into it, but frankly, I don't think it can be caused by this: the window is locked anyway (usually) at this point, so an additional lock really shouldn't matter at all.
Ok, then it could be some other change, but could also be this :)
back trace