Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346033 - crash in cocoa [WebHTMLView scrollWheel:]
Summary: crash in cocoa [WebHTMLView scrollWheel:]
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-17 02:26 EDT by Lakshmi P Shanmugam CLA
Modified: 2019-09-15 04:14 EDT (History)
0 users

See Also:

Attachments
I just experienced the same problem. (90.06 KB, text/plain)
2011-08-09 08:17 EDT, Greg Watson CLA 		no flags Details
Crash log for SWT 3.7 bus error (105.38 KB, application/octet-stream)
2011-11-15 14:21 EST, Anthony Harrison CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi P Shanmugam CLA 2011-05-17 02:26:38 EDT 
Opening bug based on comment --> https://bugs.eclipse.org/bugs/show_bug.cgi?id=341402#c20.
Crash log --> https://bugs.eclipse.org/bugs/attachment.cgi?id=195801
Comment 1 Greg Watson CLA 2011-08-09 08:17:13 EDT 
Created attachment 201134 [details]
I just experienced the same problem.
Comment 2 Anthony Harrison CLA 2011-11-15 14:21:58 EST 
Created attachment 207046 [details]
Crash log for SWT 3.7 bus error

I've been running into hard SWT crashes all day, and it looks to be a similar pattern as above.
Comment 3 Grant Gayed CLA 2011-11-15 14:42:51 EST 
re: comment 2

Your attached stack looks different from the others, so please log a separate report with swt for what you're seeing.  I notice that you're using birt, so your steps for reproducing the problem will need to include info such as which additional eclipse plug-ins to install, etc.
Comment 4 Eclipse Genie CLA 2019-09-15 04:14:00 EDT 
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.

--
The automated Eclipse Genie.