Bug 363259 - Both 32 and 64 bit versions return error 998 upon opening.
Summary: Both 32 and 64 bit versions return error 998 upon opening.
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.0 Release Candidate
Platform: Microsoft Windows Microsoft Windows
: NOR grave
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-19 05:47 UTC by Bruno de Souza Lino
Modified: 2016-05-23 11:54 UTC (History)
2 users (show)

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

Attachments
Screenshot of both versions displaying the error (684.92 KB, image/png)
2016-05-19 05:48 UTC, Bruno de Souza Lino 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno de Souza Lino 2016-05-19 05:47:53 UTC 
None of the Windows build of RC1 open. They both return 'LoadLibrary failed with error 998: Invalid access to memory location.' and don't open after you click 'ok'. Running either as admnistrator doesn't make any difference. Same for compatibility modes. The program is unusable if it can't even open. The version prior to RC1 opened normally.

Reproducible: Always

Steps to Reproduce:
1. Open krita.

Actual Results:  
Returns 'LoadLibrary failed with error 998: Invalid access to memory location.'

Expected Results:  
Krita should open.

Windows 10 x64 Home version.
Comment 1 Bruno de Souza Lino 2016-05-19 05:48:55 UTC 
Created attachment 99065 [details]
Screenshot of both versions displaying the error
Comment 2 Halla Rempt 2016-05-19 06:08:58 UTC 
That is strange, since I tested both on a Windows 10 Thinkpad and a Windows 10 Surface Pro 3, and also on a Win7 VM, and I had no problems starting either.
Comment 3 Bruno de Souza Lino 2016-05-19 18:29:21 UTC 
I find it weird as well, since the earlier version worked normally.
Comment 4 Dmitry Kazakov 2016-05-20 14:39:46 UTC 
It might be related to the new openGL version checks added to the latest version
Comment 5 Halla Rempt 2016-05-20 14:43:54 UTC 
No: those checks aren't in the release candidate builds. I made the builds on Tuesday night, and implemented the checks on Wednesday.
Comment 6 Bruno de Souza Lino 2016-05-21 15:40:00 UTC 
Is there anything I could send that should help diagnose the issue better?
Comment 7 Halla Rempt 2016-05-23 11:51:02 UTC 
Not that I know, I'm afraid. You could try the dev builds I made on Friday to see if those work better, but I cannot even guess what's up...
Comment 8 Halla Rempt 2016-05-23 11:52:20 UTC 
This link is interesting, though:

https://forums.adobe.com/thread/896692

It suggests that a firewall or virus scanner might have blocked one of krita's dll's.
Comment 9 Halla Rempt 2016-05-23 11:54:21 UTC 
Hm, and http://steamcommunity.com/app/218820/discussions/1/864975026766882300/?l=dutch suggests it might be something to do with AMD drivers. In any case, this is not a bug in Krita, but an issue on your system.