Cloned tab with "Design view" capability has no content inside

[PetrMiksik]

Apache NetBeans version

Apache NetBeans 24

What happened

When you clone the tab which have the "Design View" capability available, its content is empty. It's necessary to perform some kind of "refresh" operation to display its content (for example to switch between Design and Source View).

Language / Project Type / NetBeans Component

Java Project with Ant

How to reproduce

See the issue description.

Did this work correctly in an earlier version?

No / Don't know

Operating System

Ubuntu 22.04
Windows 10
Windows 11

JDK

OpenJDK 64-Bit JRE 21.0.5+11-Ubuntu-1ubuntu122.04
Eclipse Temurin OpenJDK 23.0.1+11

Apache NetBeans packaging

Apache NetBeans provided installer

Anything else

No response

Are you willing to submit a pull request?

No

[matthiasblaesing]

Works as expected on JDK 23 on Ubuntu 24.10:

Please check if the problem persist with a clean userdir (user command line option --userdir to point it to an empty directory.
Please also check/provide $HOME/.netbeans/24/var/log/messages.log

[neilcsmith-net]

Likewise cannot replicate with the community installer DEB (using Azul JDK 23 or same system JDK 21, and using Metal LaF) on Ubuntu 22.04.

[PetrMiksik]

I tried several system / java version / L&Fs combinations and got still the same behavior (Windows 10 - Microsoft JDK 21.0.5, Windows 11 - Eclipse Temurin JDK 23.0.1, L&F - Metal, Nimbus, FlatLaf, Native). Running NetBeans with clean userdir also did not solve the issue. Log file included.

messages.log

[mbien]

tested the lower bound too:

  Product Version         = Apache NetBeans IDE 24
  Operating System        = Linux version 6.6.65-1-MANJARO running on amd64
  Java; VM; Vendor        = 17.0.14; OpenJDK 64-Bit Server VM 17.0.14+7-LTS; Amazon.com Inc.

[matthiasblaesing]

The message log does show nothing interesting. I notice two things that stand out:

• The kernel is ancient (2 years)
• You are using KDE

Please check if running with a clean Ubuntu fixes the issue and then test whether introducing KDE or the old kernel generates the problem.