https://bugs.kde.org/show_bug.cgi?id=507547
--- Comment #1 from Mladen Milinkovic, Max <[email protected]> --- Thanks for the report. I cannot reproduce it here. > - failed assertion: 'm_ref' is null, but it shouldn't I would appreciate exact message that is written - it should says something like: ASSERT: "zzzzzzzz" in file xxxxxxx/xxxxx.cpp, line yyy > According to C++ specs, in release builds, program behaviour after the failed > assertion is undefined, though in practice it is not. According to C++ specs? > SOFTWARE/OS VERSIONS > - shouldn't matter It shouldn't, but please: - What OS and version are you using? - What compiler and version are you using? Is it one shipped with that OS/distribution? - What Qt version are you using? Is it one shipped with that OS/distribution? If the assert says: ASSERT: "m_ref != nullptr" in file ........./subtitleline.cpp, line 230 your compiler is optimizing too much away and not calling object constructors when resizing vectors. I saw this happen in some old Linux Mint build worker, but was unable to reproduce it anywhere. -- You are receiving this mail because: You are watching all bug changes.
