zamtmn / metadarkstyle

74 stars 22 forks source link

Lazarus crashes when trying to open the "IDE Options" window #24

Closed flowCRANE closed 1 year ago

flowCRANE commented 1 year ago

Lazarus 2.2.6 stable, fresh MetaDarkStyle installed (metadarkstyledsgn226 package) — when trying to open IDE Options window, the error messagebox is shown, so I can't open the window mentioned. After uninstalling the MetaDarkStyle package the IDE starts to work properly (tested), so this package causes this problem.

image

zamtmn commented 1 year ago

I try with Lazarus 2.2.6 (rev lazarus_2_2_6) FPC 3.2.2 i386-win32-win32/win64 it works, no reproduced. Please provide stacktrace

flowCRANE commented 1 year ago

Here is the stack trace:

using config file D:\Applications\LazarusDark\lazarus.cfg
SetPrimaryConfigPath NewValue="C:\Users\furious programming\AppData\Local\lazarusdark" -> "C:\Users\furious programming\AppData\Local\lazarusdark"
Hint: (lazarus) [TMainIDE.ParseCmdLineOptions] PrimaryConfigPath="C:\Users\furious programming\AppData\Local\lazarusdark"
Hint: (lazarus) [TMainIDE.ParseCmdLineOptions] SecondaryConfigPath="D:\Applications\LazarusDark"
{EW}[MetaDarkStyle]DSScheme prepare exception: "Access violation" in file "CustomDark"
{EW}[MetaDarkStyle]DSScheme prepare exception: "Access violation" in file "test"
Hint: (lazarus) [TBuildManager.SetBuildTarget] Old=x86_64-win64-win32 New=x86_64-win64-win32 Changed: OS/CPU=True LCL=False
TApplication.HandleException: EAccessViolation
Access violation
  Stack trace:
  $0000000100BB0806
  $00000001005A3F0B
  $00000001005A376E
  $00000001005A39EA
  $0000000100062133
  $00000001003AE39C
  $0000000100061CAF
  $00000001003AA15A
  $00000001003ACEB8
  $00000001001B51DA
  $00000001001B4D0B
  $00000001001B4C99
  $000000010003E659
  $0000000100181398
  $00000001001812E8
  $0000000100183967
  $0000000100011601
LAZARUS END - cleaning up ...
FreeFormEditor: FormEditor1=TFormEditor
Hint: (lazarus) [TMainIDE.Destroy] B  -> inherited Destroy... TMainIDE
Hint: (lazarus) [TMainIDE.Destroy] END
zamtmn commented 1 year ago

Fixed. please test

flowCRANE commented 1 year ago

Now it works properly. Thank you!