Recent

Author Topic: Memory Violation on Creating New Component  (Read 1196 times)

heejit

  • Full Member
  • ***
  • Posts: 245
Memory Violation on Creating New Component
« on: April 17, 2019, 02:55:21 pm »
1. Select New Project

2. Select New Package

3. From package window select add -> New Component

4. Select any component  and fill the detail and click on Create new Componet

5. Now I have Memory Access voilation


If I use package -> New Component No issue.

But New Package -> Add Component Memory Violation

Lazarus   : 2.0
Feepascal : 3.0.4
SVN Rev   : 60350M
OS        : Linux 64bit Ubuntu 18.04

Am I doing anything wrong????

jamie

  • Hero Member
  • *****
  • Posts: 6090
Re: Memory Violation on Creating New Component
« Reply #1 on: April 17, 2019, 11:15:17 pm »
Just tried 2.0.0 on my old Win2k.

Error
 
 "Privilege Instruction"
Please report it and show a picture of the error if you can..

https://bugs.freepascal.org/view_all_bug_page.php?page_number=1

or try the recent 2.0.2 release..
The only true wisdom is knowing you know nothing

heejit

  • Full Member
  • ***
  • Posts: 245
Re: Memory Violation on Creating New Component
« Reply #2 on: April 18, 2019, 11:34:56 am »
there is no picture Same Message Memory Violation Error Abort / continue and IDE close completely

heejit

  • Full Member
  • ***
  • Posts: 245
Re: Memory Violation on Creating New Component
« Reply #3 on: April 18, 2019, 12:06:32 pm »
Is this a BUG Do I need to report it????

jamie

  • Hero Member
  • *****
  • Posts: 6090
Re: Memory Violation on Creating New Component
« Reply #4 on: April 18, 2019, 11:42:15 pm »
Yes please do..

 Go to that link, sign up for a user account and post the problem and use this LINK here so they can reference the
issue some more.
The only true wisdom is knowing you know nothing

wp

  • Hero Member
  • *****
  • Posts: 11854
Re: Memory Violation on Creating New Component
« Reply #5 on: April 19, 2019, 12:38:10 am »
I tried on Windows 10 and Laz 2.0.0 / fpc 3.0.4 and confirm an Access Violation following the steps given. Doing the same with Lazarus trunk or Laz 2.0.2, however, does not yield this error.

So, before wasting your time with a duplicate bug report, I'd recommend to install the new Laz 2.0.2 and try again, this will be a good idea, anyway.

 

TinyPortal © 2005-2018