Memo generates access violation error

Question

Memo generates access violation error

Ariel-MN opened this issue 4 years ago · 26 comments

The Memo component generates an access violation error after changing the style of the application.

Example code:

import os
from delphivcl import *

BASE_DIR = os.path.dirname(os.path.abspath(__file__))

class MainForm(Form):

    def __init__(self, owner):
        self.Caption = "Test Memo"
        self.SetBounds(10, 10, 500, 400)
        self.Position = "poScreenCenter"

        # Memo component
        self.txtMemo = Memo(self)
        self.txtMemo.SetProps(Parent=self)
        self.txtMemo.SetBounds(10, 40, 300, 100)

        # Auto-load new style
        self.__sm = StyleManager()
        self.__load_style()

    def __load_style(self):
        self.__sm.LoadFromFile(os.path.join(BASE_DIR, "Windows11_Modern_Dark.vsf"))
        self.__sm.SetStyle(self.__sm.StyleNames[1])

def main():
    Application.Initialize()
    Application.Title = "Checking DelphiVCL4Python"
    Main = MainForm(Application)
    Main.Show()
    Application.Run()
    Main.Destroy()

if __name__ == '__main__':
    main()

Answer 1 · 2022-02-18T12:02:46.000Z

@Ariel-MN thank you to report. I will have a look on it.

Answer 2 · 2022-02-19T06:22:56.000Z

I tested with the same code you sent and found no such error. I even added one more style and printed them to the Memo. Please find the code and the GUI output result image.

import os
from delphivcl import *

BASE_DIR = os.path.dirname(os.path.abspath(__file__))

class MainForm(Form):

    def __init__(self, owner):
        self.Caption = "Test Memo"
        self.SetBounds(10, 10, 500, 400)
        self.Position = "poScreenCenter"

        # Memo component
        self.txtMemo = Memo(self)
        self.txtMemo.SetProps(Parent=self)
        self.txtMemo.SetBounds(10, 40, 300, 100)

        # Auto-load new style
        self.__sm = StyleManager()
        self.__load_style()

        self.txtMemo.Lines.Add(f"Number of loaded styles: {len(self.__sm.StyleNames)}")
        self.txtMemo.Lines.Add("The loaded Styles are:")
        self.txtMemo.Lines.Add(self.__sm.StyleNames[0])
        self.txtMemo.Lines.Add(self.__sm.StyleNames[1])
        self.txtMemo.Lines.Add(self.__sm.StyleNames[2])

    def __load_style(self):
        self.__sm.LoadFromFile(os.path.join(BASE_DIR, "Windows10SlateGray.vsf"))
        self.__sm.LoadFromFile(os.path.join(BASE_DIR, "SapphireKamri.vsf"))
        self.__sm.SetStyle(self.__sm.StyleNames[2])

def main():
    Application.Initialize()
    Application.Title = "Checking DelphiVCL4Python"
    Main = MainForm(Application)
    Main.Show()
    Application.Run()
    Main.Destroy()

if __name__ == '__main__':
    main()

The error is because you might not have permission to access the Windows11_Modern_Dark.vsf style file.

Answer 3 · 2022-02-19T07:26:11.000Z

I have all users full permission on the style file properties and have no problem using the same style file in an app with other components.

The application runs but it is impossible to interact with it as it generates this error that keeps reappearing in a loop.

Im using:

Windows 11
Python 3.10.2
delphivcl 0.1.34

In my environment the error is consistent even using other styles.

Answer 4 · 2022-02-19T08:45:55.000Z

Okay, fine. Thanks for more details. @Ariel-MN you meant that this error is getting generated when using the Memo component only and runs fine with other components? And did you try any other styles with the Memo component to test their working status with the Memo?

Answer 5 · 2022-02-19T08:54:32.000Z

Absolutely. The error only happens with the Memo component and not with others and I have tried with several styles obtaining the same result.

Answer 6 · 2022-02-19T09:04:55.000Z

Weird! You can see it running without any issue in the reply I posted above right? Maybe, we'll need to simulate your exact environment (OS and python version) and try it once. Will get back with more news as we figure out anything new on this.

Thank you so much and we appreciate you keep trying and testing more.

Answer 7 · 2022-02-19T11:21:15.000Z

Most likely something regarding the Win 11. Are you using Python x86 or x64?

Answer 8 · 2022-02-19T18:06:03.000Z

@Priyatham10 You are very welcome. Unfortunately your script produced the same result as mine in both of my environments.
@lmbelo I am using Python x86. I can confirm that it is not related to the version of Windows, I have tried it on another PC and am running into the same issue in this environment:

Windows 10
Python 3.9.7
delphivcl 0.1.34

Answer 9 · 2022-02-19T18:09:14.000Z

@Ariel-MN I will try to simulate in a similar environment as yours.

Answer 10 · 2022-03-23T23:28:05.000Z

@Ariel-MN are you still facing such error? I can't reproduce it here.

Answer 11 · 2022-03-24T08:50:46.000Z

@lmbelo yes, i still have the same problem.

Answer 12 · 2022-03-24T20:42:57.000Z

@Ariel-MN I really can't reproduce this issue. I have tried in Win 11 and even in Win 10, it's working in both.

Answer 13 · 2022-03-24T21:12:41.000Z

@lmbelo If it can be useful I can offer you access through teamviewer to one of my environments.

Answer 14 · 2022-03-24T21:16:55.000Z

@Ariel-MN It would be great.
Please, send an e-mail to lucas.belo@live.com to schedule a date.
Thank you for your interest and support.

Answer 15 · 2022-03-26T21:00:44.000Z

I was finally able to reproduce this issue under Python x64 architecture. It does run well under Python x86.

Answer 16 · 2022-03-29T21:41:58.000Z

I realized this is something regarding the new ComCtrls library. It occurs when the SystemStyle is enable, which may happen when using a comctrls32.dll >= 393216.
We have a ticket at https://quality.embarcadero.com/browse/RSP-37835.
I will provide a workaround soon.

Answer 17 · 2022-03-29T23:17:42.000Z

I have the workaround done. I hope to get it available in our next release.

Answer 18 · 2022-03-30T06:57:34.000Z

That's very good news. I'll be waiting for the new version. Thank you.

Answer 19 · 2022-04-08T16:46:09.000Z

@Ariel-MN it was solved in Delphi 11.1, as related in the ticket, then I don't need to proceed with my workaround.
have in mind if you release your own module using Delphi 11 the error will persist.

I'm working on a new release and it will be available soon.

Answer 20 · 2022-04-12T19:06:11.000Z

A new release is available 🚀

Can you try again, please?

Answer 21 · 2022-04-12T21:10:44.000Z

@lmbelo, fixed in version 1.0.39, although this new version seems to have broken compatibility with the new Class TNumberBox added in v. 1.0.38.

Answer 22 · 2022-04-12T21:15:18.000Z

Thank you to report @Ariel-MN. I will investigate this case.

Answer 23 · 2022-04-13T18:42:30.000Z

@Ariel-MN a new version containing the TNumberBox fix is out. Can you try again?

Answer 24 · 2022-04-13T20:37:32.000Z

@lmbelo, now everything works perfectly. Even other High DPI related issues have been fixed with Delphi 11.

Answer 25 · 2022-04-13T22:11:30.000Z

@lmbelo, now everything works perfectly. Even other High DPI related issues have been fixed with Delphi 11.

Fabulous 🚀

Can we close this issue?

Answer 26 · 2022-04-13T23:49:31.000Z

Sure, go ahead.