Re: [code] [textadept] Textadept 11.0 alpha 2

From: Mitchell <m.att.foicica.com>
Date: Wed, 24 Jun 2020 14:15:38 -0400 (EDT)

Hi Gabriel,

On Tue, 23 Jun 2020, Gabriel Dubatti wrote:

> Hi Mitchell,
>
> I commented a couple of calls I have in my code to buffer:colorize() and the
> problem continued.
>
> Then I commented out the call at file_types.lua @ 74 and the issue
> disappeared.
>
> I didn't notice any difference in the visualization with and without calling
> colorize().
>
> I also noticed that I can trigger this issue more easily by opening a new
> view after a reset.

I am not able to induce a crash. On file_types.lua:74, try this:

   buffer:colorize(1, math.min(buffer:position_from_line(last_line + 1), buffer.length - 1))

> When I reset TA I got this SIGSEGV from time to time (maybe they are
> related):
>
> Thread 1 "textadept" received signal SIGSEGV, Segmentation fault.
> #0  __GI___libc_free (mem=0xe1) at malloc.c:3102
> #1  0x00007ffff4cb10f3 in  () at
> /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so
>
> [snip]

This looks like a GTK input module crash, seemingly unrelated to what Textadept is doing. Is it random? Or is there a set of steps that always trigger it?

Cheers,
Mitchell

-- 
You are subscribed to code.att.foicica.com.
To change subscription settings, send an e-mail to code+help.att.foicica.com.
To unsubscribe, send an e-mail to code+unsubscribe.att.foicica.com.
Received on Wed 24 Jun 2020 - 14:15:38 EDT

This archive was generated by hypermail 2.2.0 : Thu 25 Jun 2020 - 06:42:14 EDT