Bug 368880 - Crash when multiple documents are open and one of the tabs is closed
Summary: Crash when multiple documents are open and one of the tabs is closed
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.0.1
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-16 06:06 UTC by Jennifer Reuter
Modified: 2016-09-26 12:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jennifer Reuter 2016-09-16 06:06:00 UTC
Hi I've had this issue occur during 3.0 Krita and I was hoping it was a bug only for that version, but it's been a consistent issue with 3.0.1 after installing it. I do not know if this is a problem within my setup, but here's what's happening:

I have more than one Krita document open, which can be navigated between, but attempting to close either one or the other tab (without closing Krita entirely) produces an immediate crash. This happens regardless how many tabs are open (exception: only one document is open).

I have a multi-boot computer and I haven't tried Krita 3.0.1 on my older Windows 8 boot, but I may attempt it to see if it's consistent there too.

This is the first time I've sent through a bug report so please let me know if I should provide more details! I'm also getting mixed messages on what program to use to provide a back-trace, what would be the best option?

P.S This is probably a seperate bug which I'll report in a new thread, but I think it relates to the above problem: I also can't edit anything in the first tab(s) (can't zoom, can't pan, brush marks don't appear, even though layers show change), while the latest tab (most recently opened file) is still functional.

Reproducible: Always

Steps to Reproduce:
1. Open two (or more) documents
2. Close one of the tabs

Actual Results:  
Windows shows the 'Krita has stopped working' dialogue box, then closes the program.

Expected Results:  
The selected tab closes, while leaving the other open and editable.

Other specs:
Windows 8.1 64 bit
Wacom Bamboo tablet
Switchable graphics: in-built Intel HD Graphics 4000 and switchable AMD Radeon HD 8730M
Comment 1 Jennifer Reuter 2016-09-16 08:52:37 UTC
Update: I switched off OpenGL and I had no issues with closing tabs. However, I'd rather not work without OpenGL, since it gives performance boosts.
Should I move this bug report into OpenGL Component area?
Comment 2 Halla Rempt 2016-09-19 12:48:20 UTC
Hi,

Which GPU does Krita run on? We've had some more reports about the display of the canvas being broken with some gpu/driver combinations, especially on systems with switchable graphics. Could you try to reproduce using these instructions: https://docs.krita.org/KritaFAQ#How_can_I_produce_a_backtrace_on_Windows.3F to get us a backtrace? I've only got systems with a single, non-switchable gpu, and I haven't been able to reproduce on Win7/NVidia Quadro or Win10/Intel HD5000.
Comment 3 Jennifer Reuter 2016-09-26 12:49:46 UTC
(In reply to Boudewijn Rempt from comment #2)
> Hi,
> 
> Which GPU does Krita run on? We've had some more reports about the display
> of the canvas being broken with some gpu/driver combinations, especially on
> systems with switchable graphics. Could you try to reproduce using these
> instructions:
> https://docs.krita.org/KritaFAQ#How_can_I_produce_a_backtrace_on_Windows.3F
> to get us a backtrace? I've only got systems with a single, non-switchable
> gpu, and I haven't been able to reproduce on Win7/NVidia Quadro or
> Win10/Intel HD5000.

Hello!
Sorry for the slow reply, I had to go through a number of projects.

I feel a little bit of a doofus right now. I decided to try downloading an update for my Radeon graphics card, since I was having blue screen issues with 'Watchdog' in general too. Turns out that by updating my graphics card, the multiple windows no longer crash.

For the time being, I guess that means the issue is solved. If I do notice that I can reproduce the issue again in some form, I'll give an update.

Thanks for the help anyway, Boudewijn!
Comment 4 Halla Rempt 2016-09-26 12:54:05 UTC
Thanks for checking!