https://bugs.kde.org/show_bug.cgi?id=475205
emohr changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=475205
--- Comment #6 from Benoît Tarrade ---
[And I cannot edit the later comment comment ... Damn it!]
So I was saying :
In `documentchecker.cpp::hasErrorInProject()` with my dataset :
```
// Note, I renamed some steps so that the function is easier to
https://bugs.kde.org/show_bug.cgi?id=475205
--- Comment #5 from Benoît Tarrade ---
Yo team guys !
I'm spamming again, I've done some testing and finally had the time to try the
stopwatches.
Here are my findings so far around the `documentchecker.cpp` file, in the
`hasError
--
You are
https://bugs.kde.org/show_bug.cgi?id=475205
farid changed:
What|Removed |Added
Flags||performance+
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=475205
--- Comment #4 from Benoît Tarrade ---
Hi Farid, thank you for your reply.
I just tested now with kdenlive on master branch and mlt on master branch as
well :
* kdenlive commit a89e93b672bf51f918945e1791bb8f24652bf871 -> Github Mirror
* mlt commit
https://bugs.kde.org/show_bug.cgi?id=475205
farid changed:
What|Removed |Added
CC||snd.no...@gmail.com
--- Comment #3 from farid ---
https://bugs.kde.org/show_bug.cgi?id=475205
--- Comment #2 from Benoît Tarrade ---
[Edit] : for now that's the stacktrace I have while profiling project loading
with valgrind :
```
Frame: Backtrace for Thread 1
[ 0] read (103077 x)
[ 1] QFSFileEngine::read(char*, long long) (101904 x)
https://bugs.kde.org/show_bug.cgi?id=475205
--- Comment #1 from Benoît Tarrade ---
After some digging, I can tell a few things :
* Calculating hashes at every project load for every element (more exactly
documentProducers and documentChains) takes up some time.
* Updating the timeline with Mlt
https://bugs.kde.org/show_bug.cgi?id=475205
Benoît Tarrade changed:
What|Removed |Added
Keywords||efficiency
--
You are receiving this mail
