Bug 374371 - Krita crashes on creating new canvas
Summary: Krita crashes on creating new canvas
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.1.1
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-31 03:05 UTC by Nimthora
Modified: 2017-01-25 09:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Crash log, scroll down to the bottom (94.05 KB, text/plain)
2016-12-31 03:05 UTC, Nimthora
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nimthora 2016-12-31 03:05:27 UTC
Created attachment 103106 [details]
Crash log, scroll down to the bottom

Krita crashes on creating a new canvas on a Lenovo Ideapad 110 running Windows. It is OpenGL unrelated as unticking doesn't do anything.

The crash log says Krita is accessing memory wrongly, so probably a fumble with pointers? Relevant lines are:

===============================================================================================================

krita.exe caused an Access Violation at location 00007FFEDE665620 in module libkritaimage.dll Reading from location FFFFFFFFA6E069C0.

AddrPC           Params
00007FFEDE665620 0000000000000000 00007FFEDE665716 00000000015B17C0  libkritaimage.dll!cblas_xerbla
00007FFEDE6637BA 0000000000000000 0000000000000000 00000000015B17C0  libkritaimage.dll!cblas_xerbla
00007FFEDE664045 0000000002DAF101 0000000000000001 00000000A9249F90  libkritaimage.dll!cblas_xerbla
00007FFEDE7A0B46 0000000000000000 0000000080000000 00000000A9249F90  libkritaimage.dll!operator+=<QStringBuilder<QString, char [5]>, QString>
00007FFEDE4D4A1C 0000000000000001 00000000A8C88690 00000000A8C886B0  libkritaimage.dll!KisUpdateTimeMonitor::instance
00007FFEDE4E3EA1 00000000A91663A1 00000000688990A7 00000000A9238420  libkritaimage.dll!KisImage::notifyProjectionUpdated
Comment 1 Halla Rempt 2017-01-25 09:04:28 UTC
I'm sorry, but there just isn't anything we can do without more information: we need a real debug log.