Recent

Author Topic: [SOLVED] New/Empty Project Form Close raises SIGSEGV  (Read 1374 times)

Munair

  • Hero Member
  • *****
  • Posts: 500
  • KISS (keep it simple, smart)
    • Ditrianum
[SOLVED] New/Empty Project Form Close raises SIGSEGV
« on: January 26, 2020, 11:51:12 pm »
Since the latest version of Lazarus on a freshly installed Manjaro I get a SIGSEGV with all my projects when closing the form.

I double checked this with a new empty project; closing the form with the X button also raises SIGSEGV. Putting a button on the form with either Self.Close or Application.Terminate also raises SIGSEGV.

The error is marked by this line: 00007FFFF52424E3 660f7f0424               movdqa %xmm0,(%rsp)

Anyone else able to reproduce this? What could be the problem?

UPDATE:

When I execute the application from the terminal and close it I get the following message:

An unhandled exception occurred at $00007F9A0C2E64E3:
EAccessViolation:
  $00007F9A0C2E64E3
« Last Edit: January 27, 2020, 09:33:24 am by Munair »
Lazarus 2.0.6; Manjaro, Windows

dbannon

  • Hero Member
  • *****
  • Posts: 894
    • tomboy-ng, a rewrite of the classic Tomboy
Re: New/Empty Project Form Close raises SIGSEGV
« Reply #1 on: January 27, 2020, 04:38:16 am »
Hey Munair, wild guess, you have not selected the GTK3 widget set have you ?

It is a bit prone to those crashes at exit ....

Davo
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

Munair

  • Hero Member
  • *****
  • Posts: 500
  • KISS (keep it simple, smart)
    • Ditrianum
Re: New/Empty Project Form Close raises SIGSEGV
« Reply #2 on: January 27, 2020, 09:15:49 am »
Actually it is GTK2 (installation default) that causes the problem. If I use GTK3 the SIGSEGV error is gone, but it raises other problems like not being able to fire up the color dialog, which freezes the program. GTK2 interface also looks better. So I'll stick to it for now.
Lazarus 2.0.6; Manjaro, Windows

Munair

  • Hero Member
  • *****
  • Posts: 500
  • KISS (keep it simple, smart)
    • Ditrianum
Re: New/Empty Project Form Close raises SIGSEGV
« Reply #3 on: January 27, 2020, 09:33:07 am »
Worse, it appears to be theme related. The well-known Mint-x theme causes the problem on Manjaro XFCE.
Lazarus 2.0.6; Manjaro, Windows

dbannon

  • Hero Member
  • *****
  • Posts: 894
    • tomboy-ng, a rewrite of the classic Tomboy
Re: [SOLVED] New/Empty Project Form Close raises SIGSEGV
« Reply #4 on: January 31, 2020, 12:55:50 am »
Its not a new XFCe is it ?   I know they announced they would be stripping all the 'legacy' GTK2 code out with the next release, has that happened yet I wonder ?

Davo
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

RDL

  • New Member
  • *
  • Posts: 46
Re: [SOLVED] New/Empty Project Form Close raises SIGSEGV
« Reply #5 on: February 01, 2020, 02:42:00 am »
Hello
I have the same problem with new projects
(https://i.yapx.ru/GRNKL.gif)
arch, xfce 4.14, lazarus 2.0.6
« Last Edit: February 01, 2020, 02:44:23 am by RDL »
Sorry for my english, google translation!

dbannon

  • Hero Member
  • *****
  • Posts: 894
    • tomboy-ng, a rewrite of the classic Tomboy
Re: [SOLVED] New/Empty Project Form Close raises SIGSEGV
« Reply #6 on: February 01, 2020, 07:42:55 am »
Right. Maybe a bit like that problem we were having with Ubuntu 19.10 ?  Not everything needed was being installed when you installed the GTK2 libraries.

Because its really easy, try installing appmenu-gtk2-module first. That would be too easy ....

Next, try using strace to work out what libraries are being looked for and not found.

David

Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

RDL

  • New Member
  • *
  • Posts: 46
Re: [SOLVED] New/Empty Project Form Close raises SIGSEGV
« Reply #7 on: February 01, 2020, 09:47:47 am »
strace project1
Code: Pascal  [Select]
  1. munmap(0x7f5908833000, 32768)           = 0
  2. munmap(0x7f5908859000, 32768)           = 0
  3. munmap(0x7f5908851000, 32768)           = 0
  4. munmap(0x7f5908849000, 32768)           = 0
  5. munmap(0x7f5906aa6000, 32768)           = 0
  6. munmap(0x7f5905b47000, 32768)           = 0
  7. munmap(0x7f5905c57000, 32768)           = 0
  8. munmap(0x7f5905c67000, 262144)          = 0
  9. munmap(0x7f5905ce7000, 262144)          = 0
  10. munmap(0x7f5908841000, 32768)           = 0
  11. --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} ---
  12. rt_sigprocmask(SIG_UNBLOCK, [SEGV], NULL, 8) = 0
  13. mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f5908859000
  14. mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f5908851000
  15. write(2, "An unhandled exception occurred "..., 54An unhandled exception occurred at $00007F59046884E3:
  16. ) = 54
  17. write(2, "EAccessViolation: \n", 19EAccessViolation:
  18. )    = 19
  19. mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f5908849000
  20. open("/usr/lib/librsvg-2.so.2", O_RDONLY|O_LARGEFILE) = 11
  21. fstat(11, {st_mode=S_IFREG|0755, st_size=3963048, ...}) = 0
  22. read(11, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P \4\0\0\0\0\0"..., 64) = 64
  23. lseek(11, 3962984, SEEK_SET)            = 3962984
  24. read(11, "\1\0\0\0\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\241p<\0\0\0\0\0"..., 64) = 64
  25. lseek(11, 64, SEEK_SET)                 = 64
  26. read(11, "\1\0\0\0\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 56) = 56
  27. read(11, "\1\0\0\0\5\0\0\0\0 \4\0\0\0\0\0\0 \4\0\0\0\0\0\0 \4\0\0\0\0\0"..., 56) = 56
  28. read(11, "\1\0\0\0\4\0\0\0\0\0$\0\0\0\0\0\0\0$\0\0\0\0\0\0\0$\0\0\0\0\0"..., 56) = 56
  29. read(11, "\1\0\0\0\6\0\0\0@\2449\0\0\0\0\0@\2649\0\0\0\0\0@\2649\0\0\0\0\0"..., 56) = 56
Sorry for my english, google translation!

dbannon

  • Hero Member
  • *****
  • Posts: 894
    • tomboy-ng, a rewrite of the classic Tomboy
Re: [SOLVED] New/Empty Project Form Close raises SIGSEGV
« Reply #8 on: February 01, 2020, 10:47:10 am »
thats the shortest strace dump I have ever seen !   Are you sure thats all ?

Looks like something bad happened long before we have any attempt to load libraries or anything like that.  What ever the problem is, its happening early.....

Davo
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

Munair

  • Hero Member
  • *****
  • Posts: 500
  • KISS (keep it simple, smart)
    • Ditrianum
Re: [SOLVED] New/Empty Project Form Close raises SIGSEGV
« Reply #9 on: February 01, 2020, 11:52:14 am »
It might be as simple as an ill designed theme. I have different flavors of Minwaita installed. They all have gtk2 and gtk3 designs in their theme folders. The default Minwaita causes a SIGSEGV, while Minwaita-OSX does not (there is little to no difference in appearance between the two).

Right now I have no time to figure out the difference and what exactly causes the exception, so I simply stick to the themes that work. That being said, it is my opinion that this is a GTK design flaw. Themes should not be able to compromise the interface on this level.
Lazarus 2.0.6; Manjaro, Windows