Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347295 - Crash
Summary: Crash
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Windows Server 2003
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-26 07:35 EDT by Daniel Migowski CLA
Modified: 2019-11-14 02:17 EST (History)
3 users (show)

See Also:


Attachments
Java Crash PID file (hs_err_pid8640.log) (19.47 KB, text/plain)
2011-05-26 07:35 EDT, Daniel Migowski CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Migowski CLA 2011-05-26 07:35:48 EDT
Created attachment 196651 [details]
Java Crash PID file (hs_err_pid8640.log)

This crash occurred on one of our clients machines. Please let me know if you need more information.
Comment 1 Felipe Heidrich CLA 2011-05-26 10:57:01 EDT
Do you know how to reproduce this problem ?

Do you know what is this type that shows in the stacktrace:
org.eclipse.swt.widgets.HookableDisplay.windowProc

Note that the crash is happening in a wm message that SWT is appararently not handling. I don't think SWT is at fault in this case.
Comment 2 Daniel Migowski CLA 2011-05-26 11:07:37 EDT
Yes, its a subclass of Display, that just forwards all messages to its parent, and does some notifying for them. Doesn't play a role here.
Comment 3 Daniel Migowski CLA 2011-05-26 11:48:53 EDT
Why does SWT call a setToolTipText(null) in releaseWidget at all?
Comment 4 Felipe Heidrich CLA 2011-05-27 11:53:20 EDT
(In reply to comment #3)
> Why does SWT call a setToolTipText(null) in releaseWidget at all?

Suppose the current tooltip showing belongs to the control being disposed, calling with null will hide the tooltip. This code is correct.
Comment 5 Lars Vogel CLA 2019-11-14 02:17:01 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.