SIGSEGV when trying to execute "Application.Run" lazarus / 21-General ---------------------------------------------------------------------- Weitentaaal · 2021-05-31 12:53 Hello guys, so today i did my daily pull to see my co workers work. Worked like always but after i tryed to Run the programm i got the Exception (See Atachement). Its Strange because we did this already for a like a year and never had any Problems. The Form he implemented was created (Application.CreateForm(TForm1, Form1)) and did not have any Procedures like Form.create. Here is where i get my Error: Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i procedure TControl.SetWidth(Value: Integer);   procedure CheckDesignBounds;  begin    // the user changed the width    if Value<0 then      raise EInvalidOperation.Create(        'TWinControl.SetBounds ('+DbgSName(Self)+'): Negative width '          +dbgs(Value)+' not allowed.');    if Value>=10000 then      raise EInvalidOperation.Create(        'TWinControl.SetBounds ('+DbgSName(Self)+'): Width '          +dbgs(Value)+' not allowed.');  end; begin   {$IFDEF CHECK_POSITION}  if CheckPosition(Self) then  DebugLn('[TControl.SetWidth] ',Name,':',ClassName,' ',dbgs(Value));  {$ENDIF}  if csLoading in ComponentState then  //<<<<<<< Error  begin    FReadBounds.Right := FReadBounds.Left+Value;    Include(FControlFlags, cfWidthLoaded);  end;  if [csDesigning, csDestroying, csLoading] * ComponentState = [csDesigning] then    CheckDesignBounds;  SetBounds(FLeft, FTop, Max(0, Value), FHeight);end;   Every Reply is appreciated ---------------------------------------------------------------------- engkin · 2021-05-31 13:13 Maybe a year ago you guys were using a different version of Lazarus/OS. Try the older version first and see if it works. You did not tell us much here, like what OS, FPC, Laz.. etc? and most imporant the code this form is running. You would work on this logically. Remove events one after the other, like OnCreate.. and see when the problem disappears, then you check the causing event procedure.