Lazarus would become unresponsive after trying to add a new menu item using
the Menu Editor. Don't know what the problem was. Got around it by manually
adding the menu item by editing the .LFM file while Lazarus was not running.
Also added the declaration and procedure body for the Click event in t
On Wed, 10 May 2017, Michael Van Canneyt via Lazarus wrote:
I have reported it as a bug.
https://bugs.freepascal.org/view.php?id=31791
I attached 2 backtraces to the bug report.
One when the warning happens (I put a breakpoint there)
One when the AV happens.
Hopefully this helps.
Micha
On Wed, 10 May 2017, Mattias Gaertner via Lazarus wrote:
On Wed, 10 May 2017 00:06:35 +0200 (CEST)
Michael Van Canneyt via Lazarus wrote:
[...]
> I have tested here:
> 64bit Linux Mint 18.1 Cinnamon, GTK2 version 2.24.30, Lazarus 1.9.0
> r54844 FPC 3.0.2 x86_64-linux-gtk2
This is the ex
On Wed, 10 May 2017 00:06:35 +0200 (CEST)
Michael Van Canneyt via Lazarus wrote:
>[...]
> > I have tested here:
> > 64bit Linux Mint 18.1 Cinnamon, GTK2 version 2.24.30, Lazarus 1.9.0
> > r54844 FPC 3.0.2 x86_64-linux-gtk2
>
> This is the exact version I am using. (lazarus SVN version may dif
On Tue, 9 May 2017, Michael W. Vogel via Lazarus wrote:
Am 09.05.2017 um 15:15 schrieb Michael Van Canneyt via Lazarus:
Hi,
I manage to reliably reproduce it !
1 Open attached project.
2 Double click MainMenu1 to edit
3 Under MenuItem5, delete MenuItem14,13,12,11
(I use the - button in th
Am 09.05.2017 um 15:15 schrieb Michael Van Canneyt via Lazarus:
Hi,
I manage to reliably reproduce it !
1 Open attached project.
2 Double click MainMenu1 to edit
3 Under MenuItem5, delete MenuItem14,13,12,11
(I use the - button in the menu editor)
4 The last menu item under MenuItem5 is then
- Open project
- Select a popup menu (there are several)
- Double click to edit
- Select menu item 1
- Immediatly select menu item 2
Here, the crash happens when going to the object inspector.
If you want, you can add a minimal example and explain every single step
again, what you do, to
On Mon, 8 May 2017, Michael W. Vogel via Lazarus wrote:
Am 08.05.2017 um 15:54 schrieb Michael Van Canneyt via Lazarus:
OK. It seems clear to me that something is being freed which should
not yet be
freed:
WARNING: TShadowItem.Destroy with LCLRefCount>0. Hint: Maybe the
component is proc
Am 08.05.2017 um 15:54 schrieb Michael Van Canneyt via Lazarus:
OK. It seems clear to me that something is being freed which should
not yet be
freed:
WARNING: TShadowItem.Destroy with LCLRefCount>0. Hint: Maybe the
component is processing an event?
This indicates to me that an unforeseen o
On Mon, 8 May 2017, Michael W. Vogel via Lazarus wrote:
Am 08.05.2017 um 15:09 schrieb Michael Van Canneyt via Lazarus:
I managed to produce a stacktrace. Hopefully this, combined with the
stacktrace
at the end is sufficient to solve the issue.
Michael.
(gdb) cont
Continuing.
WARNING: TSha
Am 08.05.2017 um 15:09 schrieb Michael Van Canneyt via Lazarus:
I managed to produce a stacktrace. Hopefully this, combined with the
stacktrace
at the end is sufficient to solve the issue.
Michael.
(gdb) cont
Continuing.
WARNING: TShadowItem.Destroy with LCLRefCount>0. Hint: Maybe the
compone
y
On Mon, 8 May 2017, Michael Van Canneyt via Lazarus wrote:
On Mon, 8 May 2017, Juha Manninen via Lazarus wrote:
Can you please create a proper backtrace with gdb using the latest
Lazarus trunk.
It shows also function names and parameter values etc.
I was actually able to reproduce the ac
On Mon, 8 May 2017, Juha Manninen via Lazarus wrote:
Can you please create a proper backtrace with gdb using the latest
Lazarus trunk.
It shows also function names and parameter values etc.
I was actually able to reproduce the access violation once but not
more however much I tried.
The sta
Can you please create a proper backtrace with gdb using the latest
Lazarus trunk.
It shows also function names and parameter values etc.
I was actually able to reproduce the access violation once but not
more however much I tried.
Juha
--
___
Lazarus m
On 07/05/17 13:08, zeljko via Lazarus wrote:
Not here, but using Lazarus Qt 64-bit + fpc-3.0.2.
Hi,
I can't reproduce it here either, using latest Lazarus GTK2, linux
64-bit, FPC 3.0.2
--
Victor Campillo
--
___
Lazarus mailing list
Lazarus@lists.
On Sun, 7 May 2017, Michael Van Canneyt wrote:
On Sun, 7 May 2017, Mattias Gaertner via Lazarus wrote:
On Sat, 6 May 2017 21:26:38 +0200 (CEST)
Michael Van Canneyt via Lazarus wrote:
[...]
I have not exactly been able to reproduce reliably, but the following just
triggered
it:
- Start
On 05/06/2017 09:26 PM, Michael Van Canneyt via Lazarus wrote:
Hi,
The menu editor of lazarus trunk seems highly unstable.
I've had 10+ crashes of lazarus in the last 2 hours, all due to the menu
editor.
The crash means that I get an access violation and I must actually kill
lazarus, because
On Sun, 7 May 2017, Mattias Gaertner via Lazarus wrote:
On Sat, 6 May 2017 21:26:38 +0200 (CEST)
Michael Van Canneyt via Lazarus wrote:
[...]
I have not exactly been able to reproduce reliably, but the following just
triggered
it:
- Start IDE
- Open project
- Select a popup menu (there are
On Sat, 6 May 2017 21:26:38 +0200 (CEST)
Michael Van Canneyt via Lazarus wrote:
>[...]
> I have not exactly been able to reproduce reliably, but the following just
> triggered
> it:
> - Start IDE
> - Open project
> - Select a popup menu (there are several)
> - Double click to edit
> - Select men
Hi,
The menu editor of lazarus trunk seems highly unstable.
I've had 10+ crashes of lazarus in the last 2 hours, all due to the menu editor.
The crash means that I get an access violation and I must actually kill lazarus,
because once I click away the access violation dialog, the lazarus wind
20 matches
Mail list logo
