- Mar 19, 2024
-
-
setScaleFactor(1.0) was called from the constructor, but then it would call qFuzzyCompare() with the current scale factor which was not initialized. ==2600289== Thread 10 vlc-qt: ==2600289== Conditional jump or move depends on uninitialised value(s) ==2600289== at 0xE8E56F1: qFuzzyCompare (qglobal.h:904) ==2600289== by 0xE8E56F1: ??? (flickable_scroll_handler.cpp:253) ==2600289== by 0xE8E67EB: ??? (flickable_scroll_handler.cpp:36) ==2600289== by 0xE1F5B76: QQmlElement (qqmlprivate.h:139) ==2600289== by 0xE1F5B76: ??? (qqmlprivate.h:166) ==2600289== by 0x104BE4AA: QQmlType::create(QObject**, void**, unsigned long) const (in /usr/lib/libQt5Qml.so.5.15.12) ==2600289== by 0x10502AE2: QQmlObjectCreator::createInstance(int, QObject*, bool) (in /usr/lib/libQt5Qml.so.5.15.12) ==2600289== by 0x105030AE: QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) (in /usr/lib/libQt5Qml.so.5.15.12) ==2600289== by 0x10502A04: QQmlObjectCreator::createInstance(int, QObject*, bool) (in /usr/lib/libQt5Qml.so.5.15.12) ==2600289== by 0x10503B4C: QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) (in /usr/lib/libQt5Qml.so.5.15.12) ==2600289== by 0x105050BF: QQmlObjectCreator::setupBindings(bool) (in /usr/lib/libQt5Qml.so.5.15.12) ==2600289== by 0x10509185: QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) (in /usr/lib/libQt5Qml.so.5.15.12) ==2600289== by 0x105026B5: QQmlObjectCreator::createInstance(int, QObject*, bool) (in /usr/lib/libQt5Qml.so.5.15.12) ==2600289== by 0x105030AE: QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) (in /usr/lib/libQt5Qml.so.5.15.12)
-
- Mar 18, 2024
-
-
Steve Lhomme authored
Following 4187faaa.
-
Steve Lhomme authored
Since we're only keeping the visible part of the picture, we need to be aware of the pixel offset for each plane. The VLC planes keep the visible extent, but not the position of the first visible pixels. We need to compute it ourselves.
-
Steve Lhomme authored
Missing from 41525773. It was probably broken before that.
-
Thomas Guillem authored
It is now possible to use the preparser only for parsing, only for fetching or both. Fixes #28545
-
- Mar 17, 2024
-
-
- Bug Fixes * aomedia:3523: SIGFPE in av1_twopass_postencode_update() pass2_strategy.c:4261. * aomedia:3535, b/317646516: Over reads in aom_convolve_copy_neon(). * aomedia:3543: invalid feature modifier when compiling aom_dsp/arm/aom_convolve8_neon_i8mm.c on Debian 10 with arm64 architecture. * aomedia:3545: Failed to parse configurations due to inconsistent elements between two arrays "av1_ctrl_args" and "av1_arg_ctrl_map" in aomenc.c. * oss-fuzz:66474, b/319140742: Integer-overflow in search_wiener. * Zero initialize an array in cdef search. See: https://aomedia.googlesource.com/aom/+/refs/tags/v3.8.2
-
-
-
-
-
This avoids a bit of indentation and makes it clearer what the goal of the code block is.
-
-
-
It can't be deduced with the current chroma description.
-
We don't need any alpha, so any value will do. Otherwise RGB10A2 can't be selected.
-
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Instead of wondering if a specific function need to be called locked or not. This allows few optimizations where 2 clock functions were called in a row.
-
Even if the clock is only used for functions that are not modifying the clock, it locks the clock->main_clock mutex. This change is necessary as all vlc_clock_t will need to be called with the lock held.
-
All vlc_clock_main_t functions need to be called with this lock held. This allows optimizations where 2 vlc_clock_main_t functions were called in a row.
-
i_slave represents an array size, so size_t is more suited than signed integer for that.
-
1.4.1 is a small release of dav1d, improving notably ARM and RISC-V speed - Optimizations for 6tap filters for NEON (ARM) - More RISC-V optimizations for itx (4x8, 8x4, 4x16, 16x4, 8x16, 16x8) - Reduction of binary size on ARM64, ARM32 and RISC-V - Fix out-of-bounds read in 8bpc SSE2/SSSE3 wiener_filter - Msac optimizations
-
- Mar 15, 2024
-
-
And don't send the STOPPED state from the STOPPED state. Fixes the following assert leading to an invalid state: test_src_player: ../../src/player/player.c:1195: vlc_player_Start: Assertion `!player->input->started' failed.
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
-
Thomas Guillem authored
Future events might be used by every type of clocks.
-
Thomas Guillem authored
vlc_clock_RegisterEvents become: - vlc_clock_AddListener - vlc_clock_RemoveListener Using the same mechanism than player and playlist. This will allow more controls on (future) clock events.
-
By this commit Albums in MusicArtistsAlbums are now sort wrt Release Year with no Default fallback sort criteria warnings.
-
The view in MusicArtistsAlbums was incorrectly trying to sort Albums from an Artist by "Album" which would resort to sorting them by releasing date. This commit change the sorting order for "title" to "alphabetical", matching it with how the roleToCriteria defines the order: case ALBUM_TITLE: return VLC_ML_SORTING_ALPHA; Fixes: #28505
-
This is justified just by the sheer amount of 64-bit arithmetic we do. The only point in sticking to a 32-bit VLC is binary compatibility, either for external VLC plugins, or for LibVLC applications. But VLC 4.0 will break binary compatibility on both counts, so that is moot. This constitutes a once in a decade opportunity to smoothly switch over, considering how rarely LibVLC compatibility is broken.
-
If you want to test this on something else, then update the corresponding status file, seriously.
-
The new image contains the latest version of the emscripten SDK.
-
Both `-emit-llvm` and a `.bc` output extension are needed to export bitcode since emscripten 3.1.50[^1]. Otherwise a plain object file will be created. [^1] https://github.com/emscripten-core/emscripten/commit/94b36c04dd323af066f2c1ab6d13f26eb818eb0b
-