Ticket #254 (closed defect: invalid)

Opened 9 months ago

Last modified 3 months ago

mystery crash

Reported by: notanumber Owned by: daelstorm
Priority: major Milestone: Release 1.3.0
Component: nicotine Version: SVN (checked out today)
Keywords: pango BadMatch Cc:

Description

I have been getting crashes on the svn version for the last couple months, on ubuntu gutsy and a fresh hardy also. I have searched for other tickets, but it is completely a mystery to me.

It crashes about every 1-3 days, always when I am away (or at least not when actively using it, I cannot correlate the crash to anything).

generally I get something like this: /home/notanumber/nicotine+/pynicotine/gtkgui/frame.py:2913: PangoWarning?: pango_layout_get_context: assertion `layout != NULL' failed

gtk.main()

/home/notanumber/nicotine+/pynicotine/gtkgui/frame.py:2913: PangoWarning?: pango_context_get_language: assertion `context != NULL' failed

gtk.main()

/home/notanumber/nicotine+/pynicotine/gtkgui/frame.py:2913: PangoWarning?: pango_context_get_metrics: assertion `PANGO_IS_CONTEXT (context)' failed

gtk.main()

/home/notanumber/nicotine+/pynicotine/gtkgui/frame.py:2913: PangoWarning?: pango_font_metrics_get_ascent: assertion `metrics != NULL' failed

gtk.main()

/home/notanumber/nicotine+/pynicotine/gtkgui/frame.py:2913: PangoWarning?: pango_font_metrics_get_descent: assertion `metrics !=NULL' failed

gtk.main()

Segmentation fault (core dumped)

occasionally, I will get, after some more pango warnings, this error instead of segfault: The program 'nicotine' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch? (invalid parameter attributes)'.

(Details: serial 2532290 error_code 8 request_code 59 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.)

I will provide any additional info that will help nail this down.

Attachments

Change History

Changed 3 months ago by quinox

  • status changed from new to closed
  • resolution set to invalid

A segmentation fault should never be triggered by n+, most likely you discovered a bug in python, one of the libraries used by nicotine+ or your system has incompatible libraries. From the top of my head I can tell you that some versions of PyVorbis? can trigger this. For now I'm marking it as invalid, if you feel it is a n+ after all don't hesitate to open a new bug report

Add/Change #254 (mystery crash)

Author



Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.