I am pleased to announce that we released the first beta of Qt 6.0 today. We have provided multiple pre-release snapshots of Qt 6.0 during the past months and Qt 6.0 has now reached the milestone to start the beta phase. Throughout the beta phase we will continue to provide subsequent beta releases via the online installer.
There is a huge number of things to talk about when it comes to the features and functionality of Qt 6.0, so I will leave this to the multiple detailed blog posts about Qt 6.0. We have already published many blog posts about all the cool things Qt 6.0 provides, and will continue to publish more blog posts throughout the year. In the upcoming Qt World Summit Online we have lined up many interesting talks about Qt 6.0, so please join to hear more.
After the first Qt 6.0 beta released today, we will push out multiple new beta releases using the online installer. With this approach, it is easy for users to test the new features and provide feedback. When we have reached a sufficient level of maturity we will create a release candidate of Qt 6.0. It will be made available directly via the online installer. We are not planning to publish separate blog posts for the subsequent beta releases and release candidate(s). In addition to binaries, source packages of each beta release are of course also available for those who prefer to build themselves.
I hope many of you will install the Qt 6.0 Beta releases, test and provide feedback to help us to complete Qt 6.0. For any issues you may find, please submit a detailed bug report to bugreports.qt.io. When filing a bug report, remember to mention which beta you found the issue with, check for duplicates and known issues. You are also welcome to join the discussions in the Qt Project mailing lists and developer forums.
I wish I could try the beta but without QtCharts, QtMultimedia, and QtGraphicalEffects it won't work for what we need. According to the "New Features in 6.0," both Multimedia and GraphicalEffects have been removed and won't return which means we'll either have to completely rework our GUI or stick with 5.15 forever.
QtMultimedia and other not deprecated modules should be added in later releases (https://www.qt.io/blog/qt-6.0-feature-freeze-milestone-reached). So you have to stick for a Qt5.15 not forever, but while they aren't reintroduced. Though I haven't seen any ETA on reintroduction, I'd expect they should be back not later than 6.2 (as it seems planned as LTS).
Qt3D was removed from beta1, what is the reason?
UPD: also it lacks imageformats and networkauth, is that intentional or mistake?
@Mykola: Qt 3D, Qt Image Formats and Qt Network Authorization are available via package manager and intended to be usable with Qt 6.0. More information of this is coming to the blog likely next week after we have polished the workflow a bit. Initial instructions available at: https://wiki.qt.io/Qt6_Add-on_src_package_build_using_Conan_package_manager
Thanks. So they wouldn't be published at http://download.qt.io/development_releases/qt/6.0/ , only through online installer or git?
Hm. Installed with online installer but can't find conan (and top-level "Additional libraries" node). Ok, then I'll wait for more detailed blog post.
Hi, we're looking forward to see the actual performance gains for Qt 6 core and QML, but I'm aware of that grafana has stopped reporting Qt benchmark results since Feb. Is it deprecated or under maintenance?
@Joshua: Benchmarks are running, but there are some unused sets listed in grafana pages. This is something we should clean up a bit to make it easier to follow. Generally for the performance there are multiple important functions that have gained a significant performance improvement already with Qt 6.0, but we also have some work still to do to get all parts of Qt to maximally benefit from these in the upcoming Qt 6.x releases.
There is currently no 32-bit version of Qt available for Windows in the online installer. Will it become available when Qt 6 is out of the beta phase? There are still enough 32-bit users to warrant building a 32-bit version of my software. In fact, for most apps for which performance is not critical (and addressing more than 2 GB not required) it's most convenient to publish just a single 32-bit version.
https://www.qt.io/blog/qt6-development-hosts-and-targets
https://doc-snapshots.qt.io/qt6-dev/windows.html
None lists 32bit. While I expect it would be possible to build from sources, it's unlikely there would be prebuilt/supported 32bit version for any system (except maybe embed/ARM) including Window.
I have no Qt6 installed, can anyone help to confirm this: https://bugreports.qt.io/browse/QTBUG-87774. If the issue is not exist in Qt6, I'll move to it.Thanks.
I could try later, but only Linux version.
Thanks.I have tested it on Ubuntu 20.04 x64, Qt(-5.12.8) from repo, it's OK. On windows, Qt-5.9.9-mingw32-gcc-9.3-x86 is OK too. I also tested it with an old build of Qt-4.8.7-msvc2015-x86 and it has no memory leaks.But Qt-5.12.8-msvc2019-x64(from https://github.com/martinrotter/qt5-minimalistic-builds/releases/tag/5.12.8) got the same result as Qt-5.12.9 and Qt-5.15.1. I have no other version of Qt build for testing. But I wonder that it's mostly issued by the msvc2019 build of recent version of Qt.
So, I've checked Qt 5.15.1, Qt 6 alpha, Qt 6 beta 1 on Linux (openSUSE Tumbleweed). Behaviour is similar on all three, memory somewhat increased, but I'm not sure that's leaking. Valgrind doesn't show memory leaks. Maybe that's just some heap allocation/freeing troubles or fragmentation. Have you profiled Windows version? How much memory usage goes up for your case?
The memory goes up and never decreases, even if I removed/deleted the toolbar after the refreshing-test finished. I have just updated the test case and grabed some screen shot about it's memory usage. All of them are available at https://bugreports.qt.io/browse/QTBUG-87774
I'm not saying there is no memory leak, but there are a lot of cases when memory can't go down without any leaks due to how heap is built. E.g. check this https://pastebin.com/zhw75m8J program. There is no any memory leaks. Try run it, check memory usage (it will be low), enter
0, memory usage goes up, enter0again — memory usage goes down, enter0— exit. Then try the same but entering1instead of zeros and memory, most probably, wouldn't go down, because allocatedxprevent shrinking the heap and freeing address space, though heap has a lot of free space.This case might be a heap fragmentation or some other case not very good for heap. Anyway, leak or not, it's better to reuse QAction's if it's possible.
" it's better to reuse QAction's if it's possible", Yes, this is a temporary plan. But the Qt-5.9.9-mingw32-gcc9 and Qt-4.8.7-msvc2015 builds both go well and have no memory leaks. The msvc2019 build, if I change the refresh times in the case to a large number, it's memory usage goes up over several GB(s) and never goes down. It's obviously issued by a bug.