Bug 415213 - Transform Tool Crashing Program After resizing
Summary: Transform Tool Crashing Program After resizing
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Tools/Transform (show other bugs)
Version: 4.2.8
Platform: Other Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-15 17:54 UTC by Stacey
Modified: 2020-04-24 12:57 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Image of crash dialogue box after transform tool usage. (348.56 KB, image/png)
2019-12-15 17:54 UTC, Stacey
Details
DebugView report (1.24 KB, text/plain)
2019-12-31 14:51 UTC, Stacey
Details
Krita log (256.55 KB, text/plain)
2019-12-31 14:52 UTC, Stacey
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stacey 2019-12-15 17:54:39 UTC
Created attachment 124510 [details]
Image of crash dialogue box after transform tool usage.

SUMMARY
Receiving a crash every time transform tool is used and then trying to do something else. For example doing ctrl+t, resizing, pressing enter and then clicking away or selecting another tool. I have tried other versions such as nightly plus, the portable version and nightly next and all produce the same result. I have used Krita for over a year with no issues before. I have tried to obtain a debug report but cannot locate the kritacrash file in any of my directory despite using %LocalAppData% and %APPDATA%. 


STEPS TO REPRODUCE
1. Press ctrl+t and resize an area.
2. Press enter
3. Click on another area of the canvas or swap tool and wait a moment.
4. Program will then come up with a crash dialogue and offer to debug or close.

OBSERVED RESULT
Program will come up with crash dialogue and offer debug or close. Debug does nothing, close just closes.

EXPECTED RESULT
Resize area of image or whole image and be able to continue editing or drawing as normally.

SOFTWARE/OS VERSIONS
Windows: Windows 7 Professional Service Pack 1
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Transform tool works absolutely fine in other editing programs such as Gimp and Corel Painter, so the issue is isolated to Krita. As above, I have been unable to produce a debug file as I cannot locate a kritacrash file in any directory, even when using the search on the whole pc.
Comment 1 RamonMiranda 2019-12-15 19:26:31 UTC
I have tried to reproduce in a laptop with and nothing happens. Works fine. Maybe is a bug only related with Win 7? 
My tests were done in 4.2.8 portable 64bit in Win 10.

testing with selections, big image and small image(1024px texture) Result = ok
testing with an entire image. Everything worked fine. 
I also have tested to dissable the opengl in preferences and enable to test the transform tool with Warp mode view active. 

Sorry for not being more useful
Comment 2 Tiar 2019-12-17 18:18:07 UTC
Can you please check if you get this error in Krita Next version that you download from the website? (Download the portable version so you don't need to install).

Also it's good that you tried to find a crash log, but on Windows to get a good crash log you'd need to download a portable package and a debug package and use them together: https://docs.krita.org/en/reference_manual/dr_minw_debugger.html
Comment 3 Stacey 2019-12-17 18:46:47 UTC
(In reply to Tymond from comment #2)
> Can you please check if you get this error in Krita Next version that you
> download from the website? (Download the portable version so you don't need
> to install).
> 
> Also it's good that you tried to find a crash log, but on Windows to get a
> good crash log you'd need to download a portable package and a debug package
> and use them together:
> https://docs.krita.org/en/reference_manual/dr_minw_debugger.html

Hi thanks for the reply.

I get this error in several versions that I have tried, I never used to get this error, but have tried and get the error on the following versions and portable ones:

4.2.8
4.2.8 portable
4.2.7.1
4.2.7.1 portable
Krita Nightly Plus 4.2.8.2
Krita Nightly Next 4.3.0

I have used corresponding debugging installers with the portable versions as well and cannot locate the debugging file anywhere. If I search for kritacrash as a file, it doesn't exist.
Comment 4 Bug Janitor Service 2019-12-18 04:33:13 UTC
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.
Comment 5 Stacey 2019-12-30 23:53:00 UTC
Just wondering if theres any update on this as I haven't heard anything? I appreciate it's been the holiday period though. I'm a very regular user of Krita and currently can't use the program due to this issue. Thanks!
Comment 6 Halla Rempt 2019-12-31 08:22:30 UTC
Best use 4.2.6 for now. Dmitry is looking into this, but he's moving to a new apartment and becoming a father... So, finding a fix is taking more time than usual.
Comment 7 Tiar 2019-12-31 12:39:22 UTC
@Stacey can you please check Krita Next version again? The version on the website is: 919-g3f0ff1a86c, but you can use a newer one, I just want to make sure you checked a fresh one since you didn't say what exact versions were those that you downloaded last time.

This bug might be either bug 414672 (which is fixed already in Krita Next version) or bug 415625 (which is not fixed), and I cannot determine it without seeing a backtrace or at least debug view log. (If it isn't fixed for you on Krita Next, that means it's not bug 414672, but it might be some other bug than bug 415625...)

- can you please try to find krita.log file? This one *must* exist and it will exist in the same location as kritacrash.log file: in %localappdata%/ . (You'll see you're (most probably) in c:/Users/[username]/AppData/Local/) If you find that file, check if you searched for the kritacrash.log file in this location; if not, please check if there is this file and attach both to this bug report. If you see only one of them, please attach one of them.

- please download DebugView program: https://docs.microsoft.com/en-us/sysinternals/downloads/debugview - it's from the Microsoft site so as safe as stuff on the internet can be. Unzip it. There will be a debugview.exe file - run it (and just let it run). Then run Krita and make it crash. Then copy everything that is visible on DebugView to a new text file in a Notepad and then attach this file here.
Comment 8 Stacey 2019-12-31 14:51:15 UTC
Created attachment 124810 [details]
DebugView report

DebugView report following a crash.
Comment 9 Stacey 2019-12-31 14:52:56 UTC
Created attachment 124811 [details]
Krita log

Krita log following crash. Unable to locate kritacrash file, only file that exists is krita.log
Comment 10 Stacey 2019-12-31 14:54:39 UTC
(In reply to Tymond from comment #7)
> @Stacey can you please check Krita Next version again? The version on the
> website is: 919-g3f0ff1a86c, but you can use a newer one, I just want to
> make sure you checked a fresh one since you didn't say what exact versions
> were those that you downloaded last time.
> 
> This bug might be either bug 414672 (which is fixed already in Krita Next
> version) or bug 415625 (which is not fixed), and I cannot determine it
> without seeing a backtrace or at least debug view log. (If it isn't fixed
> for you on Krita Next, that means it's not bug 414672, but it might be some
> other bug than bug 415625...)
> 
> - can you please try to find krita.log file? This one *must* exist and it
> will exist in the same location as kritacrash.log file: in %localappdata%/ .
> (You'll see you're (most probably) in c:/Users/[username]/AppData/Local/) If
> you find that file, check if you searched for the kritacrash.log file in
> this location; if not, please check if there is this file and attach both to
> this bug report. If you see only one of them, please attach one of them.
> 
> - please download DebugView program:
> https://docs.microsoft.com/en-us/sysinternals/downloads/debugview - it's
> from the Microsoft site so as safe as stuff on the internet can be. Unzip
> it. There will be a debugview.exe file - run it (and just let it run). Then
> run Krita and make it crash. Then copy everything that is visible on
> DebugView to a new text file in a Notepad and then attach this file here.

Thank you for the reply, I have tried Krita Next again and run into the same issue. I cannot locate kritacrash file but have found krita.log so have attached this. I have also run the debugview and attached the findings from that. Many thanks!
Comment 11 Tiar 2020-01-16 12:05:39 UTC
@Stacey our developer made another fixes to the transform tool. Can you please download Krita Next version (the newest one available on the website) and see if you have any trouble with transform tool there?
Comment 12 Stacey 2020-01-17 22:40:44 UTC
(In reply to Tymond from comment #11)
> @Stacey our developer made another fixes to the transform tool. Can you
> please download Krita Next version (the newest one available on the website)
> and see if you have any trouble with transform tool there?

Hi there,
Thanks for the reply. After I obtained the DebugView and Krita log, I saw the report pointing out the version of OpenGL 2.0 when OpenGL 3.1 seemed to be required. I have ran Krita on OpenGL 2.0 before so I don't know what's changed since then, but I got frustrated and decided to upgrade my graphics card once I learnt that my on board graphics could not update any higher. I upgraded to a Nvidia Geforce GT710 which can support much higher than 3.1 and this since has fixed the issue. 
The problem therefore seemed to stem from being a user on a version of OpenGL that is older than 3.1. I don't know if that is something you guys plan to keep in place or whether you have anyone that can test the issue with an older version of OpenGL now.
As I have installed the new card, I can no longer trigger the issue. I hope this info helps in some way with later updates for Krita if it intends to stay friendly to older systems.
Comment 13 wolthera 2020-04-24 12:57:40 UTC
Alright, then I'll resolve this...