You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Pieter van den Hombergh (Jira)" <ji...@apache.org> on 2020/12/18 11:42:00 UTC
[jira] [Comment Edited] (NETBEANS-4069) netbeans crashes after
inspecting test result windows, taking down desktop on ubuntu 19.10
[ https://issues.apache.org/jira/browse/NETBEANS-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251718#comment-17251718 ]
Pieter van den Hombergh edited comment on NETBEANS-4069 at 12/18/20, 11:41 AM:
-------------------------------------------------------------------------------
I have been able to create a zip file that is selfcontained (no more parent pom) and which reproduces the issue.
It may be related to the hardware on which you run it.
In particular NVIDIA drivers or hardware seems to be involved.
On the machines on which I can reproduce the problem I do the following.
First test with triggering code disabled. That is how the zip file is configured.
Make sure you enable the test-result view. After this first test, make sure to check the'always show' button.
Then look for the text "HERE BE DANGER" and un-comment the lines that conditionally throw an NPE.
Re-run the test in this mode and while or after the test results view shows content, mouse over the red test lines.
On the machines with the severest crash, the desktop freezes up, and after some time, rubish appears on the screen.
You have to restart at least the window manager. (gdm in my case)
On a laptop on which I hava dula-graphics mode (intel graphics+nvidia) the behavior is different depending on the graphics mode.
In the optimus mode (nvidia enabled) the effect is that you get a very ugle mouse trail with bg rubish.
In the intel mode (no nvidia) it appears that other parts of the gui are blitted (graphic blit operation) next to the error text lines. In some instance
they show the top left of the IDE or other application that occupies the top left corner of the left screen (yes, dual screen setup). The screenshot is from this setup.
So the conclusion may be that the problem actually triggers a bug in nvidia stuff on linux.
I have been able to take a screenshot of that phenomenon.
The cat is my daughter's.
was (Author: homberghp):
I have been able to create a zip file that is selfcontained (no more parent pom) and which reproduces the issue.
It may be related to the hardware on which you run it.
In particular NVIDIA drivers or hardware seems to be involved.
On the machines on which I can reproduce the problem I do the following.
First test with triggering code disabled. That is how the zip file is configured.
Make sure you enable the test-result view. After this first test, make sure to check the'always show' button.
Then look for the text "HERE BE DANGER" and un-comment the lines that conditionally throw an NPE.
Re-run the test in this mode and while or after the test results view shows content, mouse over the red test lines.
On the machines with the severest crash, the desktop freezes up, and after some time, rubish appears on the screen.
You have to restart at least the window manager. (gdm in my case)
On a laptop on which I hava dula-graphics mode (intel graphics+nvidia) the behavior is different depending on the graphics mode.
In the optimus mode (nvidia enabled) the effect is that you get a very ugle mouse trail with bg rubish.
In the intel mode (no nvidia) it appears that other parts of the gui are blitted (graphic blit operation) next to the error text lines. In some instance
they show the top left of the IDE or other application that occupies the top left corner of the left screen (yes, dual screen setup).
So the conclusion may be that the problem actually triggers a bug in nvidia stuff on linux.
I have been able to take a screenshot of that phenomenon.
The cat is my daughter's.
> netbeans crashes after inspecting test result windows, taking down desktop on ubuntu 19.10
> ------------------------------------------------------------------------------------------
>
> Key: NETBEANS-4069
> URL: https://issues.apache.org/jira/browse/NETBEANS-4069
> Project: NetBeans
> Issue Type: Bug
> Components: platform - Other
> Affects Versions: 12.0, 11.3
> Environment: Ubuntu 19.10, AMD or intel, both x86_64
> openjdk version "11.0.6" 2020-01-14
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.6+10)
> OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.6+10, mixed mode)
> netbeans 12.0-beta2 (11.3 and beta1 show the same behaviour)
> Junit 5.6.0 assertj 3.15.0,
> see attachedmaven project persiahblesales.zip
> Reporter: Pieter van den Hombergh
> Assignee: Laszlo Kishalmi
> Priority: Critical
> Attachments: Screenshot from 2020-12-18 12-35-11.png, messages.log, metrics, nbcrash-20200326.png, perishablesales.zip, uigestures
>
>
> After running a unit test and trying to inspect (failing) test result in test results window,
> netbeans crashes, taking down complete desktop. in the process.
> Since it kept crashing while typing this ticket, I will create it with multiple saves in between.
> Affetced are 11.3, 12.0-beta1 and beta2, tested on two machines. One AMD, one Intel both same distro and java versions
> The problem can be reproduced with the attached maven project perishabelsales.zip.
> 1. open project
> 2. set test results window to open always
> 3. run test
> 4. click in test results window to expand submitSold test details
> IDE then crashes, taking down desktop (wait a few seconds to see the full effect).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists