https://bugs.kde.org/show_bug.cgi?id=474362
yktoo changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=474362
farid changed:
What|Removed |Added
Flags||performance+
--- Comment #8 from farid ---
(In reply
https://bugs.kde.org/show_bug.cgi?id=474362
farid changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=474362
--- Comment #6 from yktoo ---
Also, I see that in your case it's some secondary thread that causes the
SIGSEGV, for me it was the thread 1. So it's seemingly a different problem.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=474362
--- Comment #5 from yktoo ---
Well in my case it was whopping 7829 threads. Ubuntu doesn't seem to have a
parameter for # of threads per process. I tried to increase the VMA count with:
echo 60 | sudo tee /proc/sys/vm/max_map_count
But it didn't
https://bugs.kde.org/show_bug.cgi?id=474362
--- Comment #4 from Maksim K. ---
After some investigation I think I found workaround for my case (FreeBSD). I
launched kdenlive in gdb and saw that kdenlive creates a lot of threads (more
then 16000 at the crash/hang time):
Thread 16138 received
https://bugs.kde.org/show_bug.cgi?id=474362
Maksim K. changed:
What|Removed |Added
CC||maksim.e.koz...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=474362
--- Comment #2 from yktoo ---
Can anyone please help resolve that? I'm unable to open the project which is
worth many hours of work, essentially lost at the moment...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474362
--- Comment #1 from yktoo ---
Created attachment 161536
--> https://bugs.kde.org/attachment.cgi?id=161536=edit
Kdenlive project
This is the project that causes the segfault
--
You are receiving this mail because:
You are watching all bug changes.
