406602 – Crash with using QML open dialog

Bug 406602 - Crash with using QML open dialog

Summary: Crash with using QML open dialog

Status:	RESOLVED FIXED

Alias:	None

Product:	krita
Classification:	Applications
Component:	General (show other bugs)
Version:	git master (please specify the git hash!)
Platform:	Microsoft Windows Microsoft Windows

Importance:	NOR crash
Target Milestone:	---
Assignee:	Krita Bugs

URL:
Keywords:	triaged

Depends on:
Blocks:

Reported:	2019-04-16 16:07 UTC by Alvin Wong
Modified:	2022-01-24 08:40 UTC (History)
CC List:	2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
DrMingw backtrace (15.06 KB, text/plain) 2019-04-16 16:07 UTC, Alvin Wong	Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description Alvin Wong 2019-04-16 16:07:52 UTC

Created attachment 119440 [details]
DrMingw backtrace

SUMMARY

Crash when the QML open dialog is closed on second monitor and reopened on the primary monitor.

STEPS TO REPRODUCE
1. Click open file button on touch docker
2. Move the open file dialog to another monitor and close it
3. Click open file button on touch docker again

OBSERVED RESULT
Crash

EXPECTED RESULT
No crash

SOFTWARE/OS VERSIONS
Windows: 10
Qt Version:5.12.2 

ADDITIONAL INFORMATION

Comment 1 Halla Rempt 2019-04-17 09:45:55 UTC

I'm sorry, but I cannot reproduce this myself. The crash itself happens deep inside Qt, making it even harder to figure out what's up.

Comment 2 Alvin Wong 2019-04-19 12:49:43 UTC

I did some digging. It seems that Qt messed up the backing store with QQuickWidget when the KoDialog was being opened on a different screen that it previously closed. I think there is a chance that using QQuickView instead of QQuickWidget wrapped in a KoDialog might fix it.

Comment 3 Halla Rempt 2020-01-10 14:01:30 UTC

hm, I just tried that and all it does is crash :-(

Comment 4 Alvin Wong 2022-01-24 08:40:40 UTC

Now I cannot reproduce it on 5.0.2, but I tried 4.2.0 again and it is still reproducible there, so I think it can be considered fixed now, probably by newer version of Qt.