Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:Fall 1 2022 Aug 15
Description
During testing, Karthik Raveendran observed that IGB built with Azul's JDK showed a bad defect: the tabbed panels froze up.
See his comment in linked ticket IGBF-3113 for details. Here is a link to his comment. (There are other 70 comments, so use the link to save time.)
For this task, investigate why this occurred and determine the cause.
Note that IGBF-3113 has been merged to master. If further testing is unable to replicate the issue with the tabbed panels freezing, then this issue can be closed.
Attachments
Issue Links
- relates to
-
IGBF-3113 Make new Docker image with version 9 Install4J and Zulu JDKs to build IGB
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link | IGBF-1765 [ 17855 ] |
Summary | Investigate: Why do tabbed panels free in Windows IGB 9.1.10 build with 332 Zulu JDK build | Investigate: Why do tabbed panels freeze in Windows IGB 9.1.10 packaged with 332 Zulu JDK |
Summary | Investigate: Why do tabbed panels freeze in Windows IGB 9.1.10 packaged with 332 Zulu JDK | Investigate: Why do tabbed panels freeze in IGB 9.1.10 packaged with 332 Zulu JDK on Windows |
Summary | Investigate: Why do tabbed panels freeze in IGB 9.1.10 packaged with 332 Zulu JDK on Windows | Investigate: Why do tabbed panels freeze in IGB 9.1.10 packaged with Zulu JDK u332 on Windows |
Summary | Investigate: Why do tabbed panels freeze in IGB 9.1.10 packaged with Zulu JDK u332 on Windows | Investigate: Tabbed panels freeze in IGB 9.1.10 packaged with Zulu JDK u332 on Windows |
Description |
During testing, [~karthik] observed that IGB built with Azul's JDK showed a bad defect: the tabbed panels froze up.
See comments in linked ticket for details. For this task, investigate why this occurred and determined the cause. |
During testing, [~karthik] observed that IGB built with Azul's JDK showed a bad defect: the tabbed panels froze up.
See comments in linked ticket for details. Here is a [link to his comment|https://jira.bioviz.org/browse/IGBF-3113?focusedCommentId=35648&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-35648]. For this task, investigate why this occurred and determined the cause. |
Description |
During testing, [~karthik] observed that IGB built with Azul's JDK showed a bad defect: the tabbed panels froze up.
See comments in linked ticket for details. Here is a [link to his comment|https://jira.bioviz.org/browse/IGBF-3113?focusedCommentId=35648&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-35648]. For this task, investigate why this occurred and determined the cause. |
During testing, [~karthik] observed that IGB built with Azul's JDK showed a bad defect: the tabbed panels froze up.
See his comment in linked ticket For this task, investigate why this occurred and determined the cause. |
Description |
During testing, [~karthik] observed that IGB built with Azul's JDK showed a bad defect: the tabbed panels froze up.
See his comment in linked ticket For this task, investigate why this occurred and determined the cause. |
During testing, [~karthik] observed that IGB built with Azul's JDK showed a bad defect: the tabbed panels froze up.
See his comment in linked ticket For this task, investigate why this occurred and determined the cause. |
Description |
During testing, [~karthik] observed that IGB built with Azul's JDK showed a bad defect: the tabbed panels froze up.
See his comment in linked ticket For this task, investigate why this occurred and determined the cause. |
During testing, [~karthik] observed that IGB built with Azul's JDK showed a bad defect: the tabbed panels froze up.
See his comment in linked ticket For this task, investigate why this occurred and determine the cause. Note that |
Rank | Ranked higher |
Assignee | Karthik Raveendran [ karthik ] |
Priority | Major [ 3 ] | Blocker [ 1 ] |
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | To-Do [ 10305 ] |
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
Resolution | Done [ 10000 ] | |
Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
Upon initial testing of IGB 9.1.10 packaged with Zulu JDK u332 on Windows , I was unable to replicate the issue and Dr. Loraine's mentioned in this comment , this could have been a code issue (and not an environment or installer issue).
The installers used during testing are master.exe from the download section of IGB bitbucket repo and branch specific installer, IGBF-3113.exe , from Dr. Loraine's IGB repo. Before each installation, IGB folder (AppData) was purged.