Bug 423876 (LogicMuch) - Project crashes when ever I try to open it
Summary: Project crashes when ever I try to open it
Status: RESOLVED WORKSFORME
Alias: LogicMuch
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: 4.3.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-04 17:05 UTC by LogicMuch
Modified: 2020-08-26 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
I was told to attach this by developer on reddit (3.30 KB, text/plain)
2020-07-04 17:09 UTC, LogicMuch
Details
This is the krita log (2.57 MB, text/plain)
2020-07-05 02:02 UTC, LogicMuch
Details
System Info that was also asked for. (2.44 KB, text/plain)
2020-07-05 02:05 UTC, LogicMuch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description LogicMuch 2020-07-04 17:05:26 UTC
SUMMARY
Every other project works fine it only that ONE.As soon as I try to open it everything freezes and it slows down my computer alot. Krita doesnt respond. I first had to problem in 4.2.9 and decided to see if updating it would fix the problem it didnt im on 4.3.0 and its exactly the same

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 LogicMuch 2020-07-04 17:09:08 UTC
Created attachment 129899 [details]
I was told to attach this by developer on reddit
Comment 2 Halla Rempt 2020-07-04 17:18:18 UTC
Um... You were expected to follow the instructions and attach the backtrace, not the instructions on getting a backtrace.

Also:

* please make the file that crashes available
* also attach the contents of help->system info for bug reports
* And help->krita log for bug reports.
Comment 3 LogicMuch 2020-07-04 23:36:46 UTC
(In reply to Boudewijn Rempt from comment #2)
> Um... You were expected to follow the instructions and attach the backtrace,
> not the instructions on getting a backtrace.
> 
> Also:
> 
> * please make the file that crashes available
> * also attach the contents of help->system info for bug reports
> * And help->krita log for bug reports.

"If it crashes in 4.3.0, can you please report a bug on bugs.kde.org? Please attach a crash log: https://docs.krita.org/en/reference_manual/dr_minw_debugger.html"

They didnt tell me to follow the instructions ;-;
Comment 4 LogicMuch 2020-07-05 02:02:14 UTC
Created attachment 129913 [details]
This is the krita log

I tried to also attach the file that keeps crashing but its to big I have its only like a one minute animation I dont understand.
Comment 5 LogicMuch 2020-07-05 02:05:32 UTC
Created attachment 129914 [details]
System Info that was also asked for.
Comment 6 Halla Rempt 2020-07-05 09:44:30 UTC
Hm, could you also make the actual file that crashes krita available? And can you check what happens if you don't put the file in a folder that contains exclamation marks (!!!) ?
Comment 7 LogicMuch 2020-07-05 19:57:32 UTC
Ok I put the krita file in a different folder didnt change anything. I dont know how to make the krita file available to you since it says the file is to big.
Comment 8 LogicMuch 2020-07-05 22:17:50 UTC
(In reply to LogicMuch from comment #7)
> Ok I put the krita file in a different folder didnt change anything. I dont
> know how to make the krita file available to you since it says the file is
> to big.

Could I send it by email instead?
Comment 9 Halla Rempt 2020-07-06 11:30:58 UTC
Yes, please send it to boudewijnrempt@gmail.com
Comment 10 LogicMuch 2020-07-06 12:25:49 UTC
Ok its 2.1G so its gonna take a while
Comment 11 Halla Rempt 2020-07-06 13:16:43 UTC
Ok, wow... That almost sounds like the project cannot be opened because it will make Krita run out of memory.
Comment 12 LogicMuch 2020-07-06 13:18:24 UTC
Well it shouldnt because its barely a minute long animation thats is the thing. Why are you so rude.
Comment 13 Halla Rempt 2020-07-06 13:27:45 UTC
How was that rude? In any case, a .kra file that is 2,1GB compressed on disk will take a lot of memory, and that might be the reason you cannot open it anymore. Your attempt at sending me the kra file failed, by the way.
Comment 14 Tiar 2020-07-06 13:29:45 UTC
A minute-long project can definitely make Krita run out of memory. It's 60 seconds, if you have for example 24 frames per second, you get 60*24 = 1440 frames, then if you have a few layers, let's say 4, you have 5760 frames, then if your frame is fullHD with default colorspace it would be 8294400*5760 bytes, and it is around 44 GB of RAM. And Krita needs memory for one more layer to save the preview, too.

I don't know how many frames you have since I don't have access to this file. But if it's just super big as Boud says, you can try to do it this way:

Go to Krita -> Configure Krita -> Performance, and make sure Krita can use quite a lot of RAM (leave 1-2GB for the system) and that the swap file size is as big as you can make it, I think max is 64GB. Make sure you have space on your hard drive for such a big swap file. Swap file is like your second RAM if there is not enough actual RAM (it's much slower though). Try to open the file. (Also make sure that your browser is closed etc., to leave as much RAM for Krita as possible).

There is also a way to open the file even in such case if you modify a bit the original file so you only load one layer. But let's hope the first solution will be enough.

After opening the file this way, please try to make it smaller. The memory widget on the bottom bar will tell you how big the file is in memory.
Comment 15 LogicMuch 2020-07-06 13:33:58 UTC
Ok trying that ^^
Comment 16 Halla Rempt 2020-07-06 13:46:09 UTC
Note that there's a memory warning label in the bottom statusbar that turns red if your image is getting too big. You can click on it to see more details.
Comment 17 LogicMuch 2020-07-06 13:52:12 UTC
Closed tabs out and put the swap size very high and it still didnt work sorry. The project was 12 fps and it had alot of layers but I merged them and the layers were pretty much in the same area it wouldnt go over 1,000 frames the only thing I did different this time was change the dimensions of the project and use the air brush barely. Also the kra file is finally sending.
Comment 18 LogicMuch 2020-07-06 13:53:39 UTC
It was yellow at the time and it said it needed more ram and I went to settings a switched a few things and it didnt do much.
Comment 19 Halla Rempt 2020-07-06 14:51:38 UTC
Hm, I haven't received the file yet?
Comment 20 Emmet O'Neill 2020-07-27 18:13:23 UTC
(Setting this as NEEDSINFO for now. Sounds like an out-of-memory crash.)
Comment 21 Bug Janitor Service 2020-08-11 04:33:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 22 Bug Janitor Service 2020-08-26 04:33:18 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!