Random crashes after 0.4 Development build 496 update

[Cesar Canassa]

I started noticing some random crashes in Scribes after updating it to the 0.4 Development build 496. I was not able to create a procedure to reproduce the crash, but it seems to happen every 30 min more or less.

When the crash occurs, all Scribes instances just closes without any error message.

If there is any log or crash report that can help you tracing this issue please tell, I will gladly include it in this report.

I am currently using Ubuntu 11.04

Thanks,
Cesar Canassa

[Mystilleef (mystilleef)]

Thanks for the feedback. The problem is in the new word
completion system. Disable word completion
(ctrl+shift+alt+c) and see if you can still reproduce the
crash.

 status inprogress
 importance high
 assignee mystilleef

[Mystilleef (mystilleef)]

Fixed in latest release. Please reopen if you can still reproduce the bug.

[Erik Seres (erikseres)]

Scribes still quits on me on a random basis by closing all open windows. The crash always appears to happen when I start scrolling one of the windows with the mouse wheel.

I am using version 799 on ubuntu 10.04.

Thanks,
Erik

[Cesar Canassa (cesar-canassa)]

Scribes seems much more stable with this new release, but I got a crash too a few minutes ago (after playing around with it for 6+ hours), the crash happened when I hit Ctrl+O and started browsing my project directory

[Mystilleef (mystilleef)]

Can you give me the details of scribes -i ?

[Cesar Canassa (cesar-canassa)]

This is mine:

========================================================
System Info: ('Linux', 'nyarlathotep', '2.6.35-24-generic', '#42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010', 'x86_64')
Python Version: 2.6.6 (r266:84292, Sep 15 2010, 16:22:56)
[GCC 4.4.5]
System Byteorder: little
Python Modules: ('__builtin__', '__main__', '_ast', '_bisect', '_codecs', '_collections', '_functools', '_hashlib', '_locale', '_random', '_socket', '_sre', '_ssl', '_struct', '_symtable', '_warnings', '_weakref', 'array', 'binascii', 'cPickle', 'cStringIO', 'errno', 'exceptions', 'fcntl', 'gc', 'grp', 'imp', 'itertools', 'marshal', 'math', 'operator', 'posix', 'pwd', 'select', 'signal', 'spwd', 'strop', 'sys', 'syslog', 'thread', 'time', 'unicodedata', 'xxsubtype', 'zipimport', 'zlib')
========================================================
Scribes Version: 0.4-dev-build799
Dbus Version: (0, 83, 0)
GTK+ Version: (2, 22, 0)
PyGTK Version: (2, 21, 0)
Psyco Not Installed
========================================================
Running Instance: 1
========================================================
Python Path: /usr/lib/python2.6/dist-packages
Plugin Path: /usr/lib/scribes/GenericPlugins
Data Path: /usr/share/scribes
Executable Path: /usr/bin
========================================================

[Erik Seres (erikseres)]

And mine is this:

========================================================
System Info: ('Linux', 'ZengoLaptop', '2.6.37-12-generic', '#26~lucid1-Ubuntu SMP Wed Jan 5 22:55:10 UTC 2011', 'x86_64')
Python Version: 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3]
System Byteorder: little
Python Modules: ('__builtin__', '__main__', '_ast', '_bisect', '_codecs', '_collections', '_functools', '_hashlib', '_locale', '_random', '_socket', '_sre', '_ssl', '_struct', '_symtable', '_warnings', '_weakref', 'array', 'binascii', 'cPickle', 'cStringIO', 'errno', 'exceptions', 'fcntl', 'gc', 'grp', 'imp', 'itertools', 'marshal', 'math', 'operator', 'posix', 'pwd', 'select', 'signal', 'spwd', 'strop', 'sys', 'syslog', 'thread', 'time', 'unicodedata', 'xxsubtype', 'zipimport', 'zlib')
========================================================
Scribes Version: 0.4-dev-build799
Dbus Version: (0, 83, 0)
GTK+ Version: (2, 20, 1)
PyGTK Version: (2, 17, 0)
Psyco Not Installed
========================================================
Running Instance: 0
========================================================
Python Path: /usr/lib/python2.6/dist-packages
Plugin Path: /usr/lib/scribes/GenericPlugins
Data Path: /usr/share/scribes
Executable Path: /usr/bin
========================================================

[Erik Seres (erikseres)]

Update: since I have upgraded to version 820, the crash appears to occur more often. I have had it crash up to 5 times a minute since. Previously, the crash would occur once every few minutes to once every few hours. So, this may just be a coincidence or the situation may have worsened.

Thanks for this otherwise great tool!
Erik

[Mystilleef (mystilleef)]

Can you provide the errors at the command line when it crashes?

[Erik Seres (erikseres)]

I normally don't launch Scribes from the command line. I have source code files associated with Scribes and open them by double clicking them. But for the test you are requesting, I will launch now from the command line.

[Erik Seres (erikseres)]

This error showed up in the terminal after scribes had quit on me:

Forcing the editor to quit. Damn something is wrong!
Forcing the editor to quit. Damn something is wrong!
====================================================
Module: InstanceManager.py
Class: Manager
Method: unregister_editor
Exception Type: ValueError
Error: Instance not found <Editor object at 0x31fceb0 (SCRIBES+SIGNALS+Signals at 0x2c12800)>
====================================================
The program 'Scribes' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 676453 error_code 11 request_code 138 minor_code 2)
  (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.)

[Mystilleef (mystilleef)]

Can you explain exactly what you were doing before that happened?

For example did you close a file and reopen it immediately? Where you typing when it happened? How many windows did you have open?

The more info I can get to reproduce the problem, the better.

Also what type of document where you working on, PHP, Python, XML?

[Erik Seres (erikseres)]

I have had it occur with a single window or many, maybe 20-30, windows open. It will always occur when I scroll a window. I want to say that it crashes when I _start_ scrolling the window but I am not 100% on that. So, it may just be at any time during the scrolling.

I can not correlate it to any other activities, so I don't think it has to do with quickly closing and reopening a file.

I edit Erlang and C source files. I am running Ubuntu Lucid 64-bit with the latest updates. This is an ASUS UL30Vt laptop with 4GB RAM, 64-bit system.

Let me know what other information you need...

Thank you!

[Erik Seres (erikseres)]

Forgot to say that I never have had it occur during typing, I am certain about that.

[Mystilleef (mystilleef)]

Thank you. That's good enough.

[Mystilleef (mystilleef)]

Erik, please test revision 828 to reproduce the scroll crashing bug.

[Erik Seres (erikseres)]

Thanks for the code updates! Unfortunately, the crash still occurs. Although, in four hours of use, it only happened once.

[Erik Seres (erikseres)]

Actually, it is happening again very often. Like in the last 5 minutes, I got 4 crashes. The command line error message is the same that I posted yesterday.

[Mystilleef (mystilleef)]

Erik are you by chance using an xorg-server from a ppa package? That error look earily like a problem with the xorg-server. So what version or xorg-server do you have installed?

[Erik Seres (erikseres)]

X -version

X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-28-server x86_64 Ubuntu
Current Operating System: Linux ZengoLaptop 2.6.37-12-generic #26~lucid1-Ubuntu SMP Wed Jan 5 22:55:10 UTC 2011 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.37-12-generic root=UUID=42608516-bffa-44a7-80e2-ffb3ccea4a3c ro rootflags=commit=100 quiet splash
Build Date: 10 December 2010 05:52:57PM
xorg-server 2:1.7.6-2ubuntu7.5 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.16.4
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.

[Mystilleef (mystilleef)]

I've reviewed all the code I checked in since the last
major PPA update and I don't see anything that could make
Scribes crash due to scrolling.

Most of the updates in those releases pertained to the word
completion system. I've addressed many of the potential
problems with the word completion system.

Build 849 is available. Could you test with word completion
enabled and disabled? Press ctrl+shift+alt+c to toggle
word completion.

I'll invite other 64-bit users to see if they can reproduce
this problem.

Thanks for helping.

[Erik Seres (erikseres)]

Thanks for the updates. With version 849, I still get the crashes while scrolling. This is with and without word completion enabled.

[Erik Seres (erikseres)]

The crashes seem to come in bursts. I was able to work for about 5 hours in a row with a crash or two. In the past half hour, I got a crash every minute or so. Note, that my work pattern has not changed in any way (that I noticed anyway) during the past half hour.

[Erik Seres (erikseres)]

I have an interesting discovery. Out of desperation from the very frequent crashes, I have decided to go back to version 599 with which I had not had any problems. And now it will crash the same way as any recent versions. So, I guess the problem is outside of Scribes. Interestingly, however, only Scribes crashes, nothing else. Thanks for your patience but I think at this point it is up to me to figure out what is wrong with my system.

[Mystilleef (mystilleef)]

Based on the error message, I suspect it's a problem with X, your graphics driver or the kernel. Did you upgrade any of these?

[quarx (samson-sap)]

I have crashes after updating to build 849, it occurs after opening 2nd or 3rd file one after another, 2nd or 3rd window cannot load the menu. I have noticed also even if it is running ok, CPU utilization is constant at 96%

[Mystilleef (mystilleef)]

quarx can you report the error message you get when the crash occurs?

Also provide scribes -i

[quarx (samson-sap)]

there are no error messages on crashes, first instance of scribes can still be accessed and usable, it is just other new started instances are freezing.

System Info: ('Linux', 'samson-desktop', '2.6.35-25-generic', '#44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011', 'x86_64')
Python Version: 2.6.6 (r266:84292, Sep 15 2010, 16:22:56)
[GCC 4.4.5]
System Byteorder: little
Python Modules: ('__builtin__', '__main__', '_ast', '_bisect', '_codecs', '_collections', '_functools', '_hashlib', '_locale', '_random', '_socket', '_sre', '_ssl', '_struct', '_symtable', '_warnings', '_weakref', 'array', 'binascii', 'cPickle', 'cStringIO', 'errno', 'exceptions', 'fcntl', 'gc', 'grp', 'imp', 'itertools', 'marshal', 'math', 'operator', 'posix', 'pwd', 'select', 'signal', 'spwd', 'strop', 'sys', 'syslog', 'thread', 'time', 'unicodedata', 'xxsubtype', 'zipimport', 'zlib')
========================================================
Scribes Version: 0.4-dev-build849
Dbus Version: (0, 83, 0)
GTK+ Version: (2, 22, 0)
PyGTK Version: (2, 21, 0)
Psyco Not Installed
========================================================
Running Instance: 0
========================================================
Python Path: /usr/lib/python2.6/dist-packages
Plugin Path: /usr/lib/scribes/GenericPlugins
Data Path: /usr/share/scribes
Executable Path: /usr/bin

[Mystilleef (mystilleef)]

quarx, I think the problem you're having is different from Erik's problem. Open another bug report and show me how to reproduce the problem you're having.

[Erik Seres (erikseres)]

Mystilleef, I normally keep my system up to date using $sudo apt-get dist-upgrade. I have not done any other trickery to any of these components.
Erik

[Mystilleef (mystilleef)]

Eric & Quarx,

Please test again with build 910. I think I may have found the problem.

Thanks

A Scribes deb file is attached.

[Mystilleef (mystilleef)]

2 people have confirmed that this has been fixed. Please test the latest branch. Reopen if you're still having problems.

[Erik Seres (erikseres)]

Since you posted your fix, I have had the crash occur three times (my work pattern has not changed, working 8-10 hours a day). This is definitely a huge improvement over having crashes every few minutes. Thank you!

[Mystilleef (mystilleef)]

Eric what version are you using?

[Erik Seres (erikseres)]

I was trying with 912. Now I am on 917 and have just run into a series of crashes in the last half hour. :( I see you are asking to try with 910 though. Should I go back to 910 and try with that?
Thanks.

[Mystilleef (mystilleef)]

Can you run

python -m trace -t /usr/bin/scribes youfile.txt

and paste the result when it crashes.

Make sure Scribes is not forking from the terminal. You can disable that in the advanced configuration window.

Thanks

[quarx (samson-sap)]

build 912 fixed my problem, I think Erik has a set of different problem.

[Erik Seres (erikseres)]

I have tried a number of times with debug trace output but Scribes would every time crawl to a halt or to a point where it is no longer responsive or unusable. And, of course, in those instances, it did not crash either... I will keep trying, just wanted to update you.

[Erik Seres (erikseres)]

I can't seem to get the crash to happen with trace output enabled. But then I am not really able to use it either with trace slowing it down. However, - and this may or may not be a clue - since your commit which you claim has fixed the issue, I think it indeed has fixed it and what I am seeing now is something different. I have just realized that now it will not crash on scrolling, instead, the crashes seem to correlate to when the window receives focus. The crashes occur a lot less often, too. So, thanks again for that fix!

[Erik Seres (erikseres)]

Just a quick update... I gave up trying to run Scribes with trace output for above reasons. However, since I installed version 954, the crashes are once again more frequent. I don't know if this is a clue or just causes confusion but I wanted to share anyway. I am considering to rebuild my system from scratch as it seems like I am the only one running into this crash issue. But then it is only Scribes crashing all the time, so I am not sure one way or the other...

[Erik Seres (erikseres)]

Interestingly, today, I had scribes crash almost constantly and I decided to give getting some trace output a try again. And, sure enough, I was able to get the crash to happen with debug trace enabled in the matter of minutes. Attached is the log output leading up to the crash. It is not the full output from when I had started Scribes but I hope it will be sufficient.

Thanks again for looking into this issue.

Erik

[Mystilleef (mystilleef)]

Eric can you test again with the latest from launchpad. I think it's build 968. Thanks for the log, it gives an idea.

[Erik Seres (erikseres)]

My test was done and the log was created with build 968.