#10739: GTalk account and long url crashes pidgin (BadAlloc)

[Pidgin]

#10739: GTalk account and long url crashes pidgin (BadAlloc)
--------------------------------------+-------------------------------------
 Reporter:  gren                      |     Owner:  darkrain42
     Type:  defect                    |    Status:  new      
Component:  Google Talk               |   Version:  2.6.2    
 Keywords:  gtalk crash url badalloc  |  
--------------------------------------+-------------------------------------
 Hi all,

 When I insert a long url in my GTalk account to a GTalk contact it crashes
 instantly my pidgin with this error :

 {{{
 The program 'pidgin' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 29741 error_code 11 request_code 53 minor_code 0)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()
 function.)
 }}}

 Just for tests I try to insert a "data" link like
 '''data:text/html;base64,{the data in base64}'''. The link is more that
 6000 chars.
 I try to repeat this error and unfortunately it made my pidgin crashes
 each time.

 The error don't occurred in a jabber account but only if I talk on GTalk
 but my contact can't see the link because it's too long (I presume GTalk
 is more restrict for that).

 I use Pidgin 2.6.2 (libpurple 2.6.2) on an updated Ubuntu 9.10.

 Best regards,
 gren

--
Ticket URL: <http://developer.pidgin.im/ticket/10739>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#10739: GTalk account and long url crashes pidgin (BadAlloc)
--------------------------------------+-------------------------------------
 Reporter:  gren                      |        Owner:  darkrain42
     Type:  defect                    |       Status:  new        
Milestone:                            |    Component:  Google Talk
  Version:  2.6.2                     |   Resolution:            
 Keywords:  gtalk crash url badalloc  |  
--------------------------------------+-------------------------------------
Description changed by gren:

Old description:

> Hi all,
>
> When I insert a long url in my GTalk account to a GTalk contact it
> crashes instantly my pidgin with this error :
>
> {{{
> The program 'pidgin' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAlloc (insufficient resources for operation)'.
>   (Details: serial 29741 error_code 11 request_code 53 minor_code 0)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error()
> function.)
> }}}
>
> Just for tests I try to insert a "data" link like
> '''data:text/html;base64,{the data in base64}'''. The link is more that
> 6000 chars.
> I try to repeat this error and unfortunately it made my pidgin crashes
> each time.
>
> The error don't occurred in a jabber account but only if I talk on GTalk
> but my contact can't see the link because it's too long (I presume GTalk
> is more restrict for that).
>
> I use Pidgin 2.6.2 (libpurple 2.6.2) on an updated Ubuntu 9.10.
>
> Best regards,
> gren

New description:

 Hi all,

 When I insert a long url in my GTalk account to a GTalk contact it crashes
 instantly my pidgin with this error :

 {{{
 The program 'pidgin' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 29741 error_code 11 request_code 53 minor_code 0)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()
 function.)
 }}}

 Just for tests I have tried to insert a "data" link like
 '''data:text/html;base64,{the data in base64}'''. The link is more that
 6000 chars.
 I have tried to repeat this error and unfortunately it made my pidgin
 crashes each time.

 The error doesn't occurred in a jabber account but only if I talk on GTalk
 but my contact can't see the link because it's too long (I presume GTalk
 is more restrict for that).

 I use Pidgin 2.6.2 (libpurple 2.6.2) on an updated Ubuntu 9.10.

 Best regards,
 gren

--

--
Ticket URL: <http://developer.pidgin.im/ticket/10739#comment:1>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#10739: GTalk account and long url crashes pidgin (BadAlloc)
--------------------------------------+-------------------------------------
 Reporter:  gren                      |        Owner:  darkrain42
     Type:  defect                    |       Status:  new        
Milestone:                            |    Component:  Google Talk
  Version:  2.6.2                     |   Resolution:            
 Keywords:  gtalk crash url badalloc  |  
--------------------------------------+-------------------------------------
Description changed by gren:

Old description:

> Hi all,
>
> When I insert a long url in my GTalk account to a GTalk contact it
> crashes instantly my pidgin with this error :
>
> {{{
> The program 'pidgin' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAlloc (insufficient resources for operation)'.
>   (Details: serial 29741 error_code 11 request_code 53 minor_code 0)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error()
> function.)
> }}}
>
> Just for tests I have tried to insert a "data" link like
> '''data:text/html;base64,{the data in base64}'''. The link is more that
> 6000 chars.
> I have tried to repeat this error and unfortunately it made my pidgin
> crashes each time.
>
> The error doesn't occurred in a jabber account but only if I talk on
> GTalk but my contact can't see the link because it's too long (I presume
> GTalk is more restrict for that).
>
> I use Pidgin 2.6.2 (libpurple 2.6.2) on an updated Ubuntu 9.10.
>
> Best regards,
> gren

New description:

 Hi all,

 When I insert a long url in my GTalk account to a GTalk contact it crashes
 instantly my pidgin with this error :

 {{{
 The program 'pidgin' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 29741 error_code 11 request_code 53 minor_code 0)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()
 function.)
 }}}

 Just for tests I have tried to insert a "data" link like
 '''data:text/html;base64,{the data in base64}'''. The link is more that
 6000 chars.
 I have tried to repeat this error and unfortunately it made my pidgin
 crashe each time.

 The error doesn't occurred in a jabber account but only if I talk on GTalk
 but my contact can't see the link because it's too long (I presume GTalk
 is more restrict for that).

 I use Pidgin 2.6.2 (libpurple 2.6.2) on an updated Ubuntu 9.10.

 Best regards,
 gren

--

--
Ticket URL: <http://developer.pidgin.im/ticket/10739#comment:2>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#10739: GTalk account and long url crashes pidgin (BadAlloc)
--------------------------------------+-------------------------------------
 Reporter:  gren                      |        Owner:  darkrain42
     Type:  defect                    |       Status:  new        
Milestone:                            |    Component:  Google Talk
  Version:  2.6.2                     |   Resolution:            
 Keywords:  gtalk crash url badalloc  |  
--------------------------------------+-------------------------------------
Description changed by gren:

Old description:

> Hi all,
>
> When I insert a long url in my GTalk account to a GTalk contact it
> crashes instantly my pidgin with this error :
>
> {{{
> The program 'pidgin' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAlloc (insufficient resources for operation)'.
>   (Details: serial 29741 error_code 11 request_code 53 minor_code 0)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error()
> function.)
> }}}
>
> Just for tests I have tried to insert a "data" link like
> '''data:text/html;base64,{the data in base64}'''. The link is more that
> 6000 chars.
> I have tried to repeat this error and unfortunately it made my pidgin
> crashe each time.
>
> The error doesn't occurred in a jabber account but only if I talk on
> GTalk but my contact can't see the link because it's too long (I presume
> GTalk is more restrict for that).
>
> I use Pidgin 2.6.2 (libpurple 2.6.2) on an updated Ubuntu 9.10.
>
> Best regards,
> gren

New description:

 Hi all,

 When I insert a long url in my GTalk account to a GTalk contact it crashes
 instantly my pidgin with this error :

 {{{
 The program 'pidgin' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 29741 error_code 11 request_code 53 minor_code 0)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()
 function.)
 }}}

 Just for tests I have tried to insert a "data" link like
 '''data:text/html;base64,{the data in base64}'''. The link is more that
 6000 chars.
 I have tried to repeat this error and unfortunately it made my pidgin
 crash each time.

 The error doesn't occurred in a jabber account but only if I talk on GTalk
 but my contact can't see the link because it's too long (I presume GTalk
 is more restrict for that).

 I use Pidgin 2.6.2 (libpurple 2.6.2) on an updated Ubuntu 9.10.

 Best regards,
 gren

--

--
Ticket URL: <http://developer.pidgin.im/ticket/10739#comment:3>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#10739: GTalk account and long url crashes pidgin (BadAlloc)
--------------------------------------+-------------------------------------
 Reporter:  gren                      |        Owner:  darkrain42
     Type:  defect                    |       Status:  pending    
Milestone:                            |    Component:  Google Talk
  Version:  2.6.2                     |   Resolution:            
 Keywords:  gtalk crash url badalloc  |  
--------------------------------------+-------------------------------------
Changes (by darkrain42):

  * status:  new => pending


Comment:

 Please follow [wiki:GetABacktrace the instructions] to get a backtrace and
 attach it to this ticket.[[BR]]You're inserting it into a conversation
 window, correct? Does it happen immediately after you insert it or when
 you attempt to send the message?

--
Ticket URL: <http://developer.pidgin.im/ticket/10739#comment:4>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#10739: GTalk account and long url crashes pidgin (BadAlloc)
--------------------------------------+-------------------------------------
 Reporter:  gren                      |        Owner:  darkrain42
     Type:  defect                    |       Status:  pending    
Milestone:                            |    Component:  Google Talk
  Version:  2.6.2                     |   Resolution:            
 Keywords:  gtalk crash url badalloc  |  
--------------------------------------+-------------------------------------
Changes (by gren):

  * status:  pending => new


Comment:

 Replying to [comment:4 darkrain42]:
 > Please follow [wiki:GetABacktrace the instructions] to get a backtrace
 and attach it to this ticket.[[BR]]You're inserting it into a conversation
 window, correct? Does it happen immediately after you insert it or when
 you attempt to send the message?

 Yes, I insert my link into a conversation window.
 The bug happen 1 sec after the insert before I attempt to send the
 message.

 By the way, the bug doesn't happen each time but after 2-3 successful link
 insert. It seems a buffer overflow problem.

 I follow the instruction to backtrace the bug but the "bt full" step give
 me a "No stack." :
 {{{
 GNU gdb (GDB) 7.0-ubuntu
 Copyright (C) 2009 Free Software Foundation, Inc.
 License GPLv3+: GNU GPL version 3 or later
 <http://gnu.org/licenses/gpl.html>
 This is free software: you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
 and "show warranty" for details.
 This GDB was configured as "i486-linux-gnu".
 For bug reporting instructions, please see:
 <http://www.gnu.org/software/gdb/bugs/>...
 Reading symbols from /usr/bin/pidgin...(no debugging symbols
 found)...done.
 (gdb) handle SIGPIPE nostop noprint
 Signal        Stop      Print   Pass to program Description
 SIGPIPE       No        No      Yes             Broken pipe
 (gdb) run
 Starting program: /usr/bin/pidgin
 [Thread debugging using libthread_db enabled]
 [New Thread 0xb7deab70 (LWP 2455)]
 [New Thread 0xb7581b70 (LWP 2496)]
 [Thread 0xb7581b70 (LWP 2496) exited]
 The program 'pidgin' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 58212 error_code 11 request_code 53 minor_code 0)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()
 function.)
 [Thread 0xb7deab70 (LWP 2455) exited]

 Program exited with code 01.
 (gdb) bt full
 No stack.
 }}}

 Best regards,
 gren

--
Ticket URL: <http://developer.pidgin.im/ticket/10739#comment:5>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#10739: GTalk account and long url crashes pidgin (BadAlloc)
--------------------------------------+-------------------------------------
 Reporter:  gren                      |        Owner:  darkrain42
     Type:  defect                    |       Status:  pending    
Milestone:                            |    Component:  Google Talk
  Version:  2.6.2                     |   Resolution:            
 Keywords:  gtalk crash url badalloc  |  
--------------------------------------+-------------------------------------
Changes (by deryni):

  * status:  new => pending


Comment:

 Please follow the directions in that "Note to programmers" message and
 report the backtrace you get as a result.

 Use "break gdk_x_error" to add the breakpoint before running pidgin, then
 run pidgin in gdb with "run --sync" and then get the backtrace like
 normal.

--
Ticket URL: <http://developer.pidgin.im/ticket/10739#comment:6>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#10739: GTalk account and long url crashes pidgin (BadAlloc)
--------------------------------------+-------------------------------------
 Reporter:  gren                      |        Owner:  darkrain42
     Type:  defect                    |       Status:  closed    
Milestone:                            |    Component:  Google Talk
  Version:  2.6.2                     |   Resolution:            
 Keywords:  gtalk crash url badalloc  |  
--------------------------------------+-------------------------------------
Changes (by trac-robot):

  * status:  pending => closed


Comment:

 This ticket was closed automatically by the system.  It was previously set
 to a Pending status and hasn't been updated within 14 days.

--
Ticket URL: <http://developer.pidgin.im/ticket/10739#comment:7>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker