You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2022/04/29 10:11:45 UTC

[Bug 66044] New: JMeter 5.5: No splash screen on startup

https://bz.apache.org/bugzilla/show_bug.cgi?id=66044

            Bug ID: 66044
           Summary: JMeter 5.5: No splash screen on startup
           Product: JMeter
           Version: 5.5
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: logox01@gmx.at
  Target Milestone: JMETER_5.5

Splash screen is no longer displayed when starting JMeter 5.5:
-tested with RC1 and RC2
-Windows 10 x64
-OpenJDK11 and OpenJDK17

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 66044] JMeter 5.5: No splash screen on startup

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=66044

logox01@gmx.at changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEEDINFO                    |RESOLVED

--- Comment #4 from logox01@gmx.at ---
Thanks for the patch - successfully tested with the last nightly (aaead67 /
Java 8, 11 and 17).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 66044] JMeter 5.5: No splash screen on startup

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=66044

Felix Schumacher <fe...@internetallee.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #2 from Felix Schumacher <fe...@internetallee.de> ---
Is no window displayed, or is the content missing?

Under linux the content is shown with Java 8 and (probably) not shown with 11
and 17 (or I am not fast enough to see it).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 66044] JMeter 5.5: No splash screen on startup

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=66044

logox01@gmx.at changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All

--- Comment #1 from logox01@gmx.at ---
Currently we are using JMeter 5.4.1 (same OS and Java), and everything is
working fine (splash screen is showing up after starting JMeter).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 66044] JMeter 5.5: No splash screen on startup

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=66044

--- Comment #3 from Felix Schumacher <fe...@internetallee.de> ---
Under linux the patch will bring back the content of the splash screen with
Java 8, 11 and 17. Could you test with Windows?

commit aaead67610cd61d486d6ae54dab7b05338bcf40a
AuthorDate: Fri Apr 29 19:31:10 2022 +0200

    Split start up phase, to give splash screen more time

    The move of method startGui into the Swing thread led
    to an empty or not visible splash screen.

    Bugzilla Id: 66044
---
 .../src/main/java/org/apache/jmeter/JMeter.java    | 36 +++++++++++++++++-----
 .../main/java/org/apache/jmeter/SplashScreen.java  |  6 +++-
 2 files changed, 33 insertions(+), 9 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 66044] JMeter 5.5: No splash screen on startup

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=66044

--- Comment #5 from Vladimir Sitnikov <si...@gmail.com> ---
Felix, I just noticed that all the splash.setProgress(40); calls do not really
work inside startGuiPartTwo since they are executed in a single Runnable.

If we really want to update progress incrementally, then we need split the
method into a sequence of smaller Runnable steps :-/
The worse is that those runnables need to reuse certain variables, so splitting
the code manually seems to be non-trivial, error-prone, and hard to maintain
:-/

I do not think "losing progress bar" is blocking for 5.5, however, I guess that
is one of the cases where coroutines might help us to keep the same linear code
while the compiler would split the code in chunks.

-- 
You are receiving this mail because:
You are the assignee for the bug.