Bug 562476 - ecllipse hangs and not able to access when click W3C WebDriver specification link and metalog error automatically displayed
Summary: ecllipse hangs and not able to access when click W3C WebDriver specification ...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7.1   Edit
Hardware: PC Windows 10
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2020-04-24 16:15 EDT by sathish k CLA
Modified: 2024-04-08 12:55 EDT (History)
1 user (show)

See Also:

Attachments
log file (969.84 KB, application/octet-stream)
2020-04-24 16:15 EDT, sathish k 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 sathish k CLA 2020-04-24 16:15:01 EDT 
Created attachment 282556 [details]
log file

when we click on W3C WebDriver specification  link in sendkeys method , a browser opened . then eclipse hangs and crashed 

error -.metalog\log generated
Comment 1 Stephan Herrmann CLA 2020-04-24 18:26:35 EDT 
The log file contains many exceptions, but first of all I see that a very old version of Eclipse is used. 

Please download a recent version and test again.
Comment 2 Eclipse Genie CLA 2022-04-15 08:40:11 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.
Comment 3 Eclipse Genie CLA 2024-04-08 12:55:04 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.