After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 665082 - Crash in javascript autocompletion
Crash in javascript autocompletion
Status: RESOLVED FIXED
Product: anjuta
Classification: Applications
Component: plugins: language-support-javascript
3.2.x
Other Linux
: High critical
: ---
Assigned To: Maxim Ermilov
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2011-11-28 20:21 UTC by Johannes Schmid
Modified: 2011-11-30 18:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Johannes Schmid 2011-11-28 20:21:49 UTC 
The original bug report doesn't have too much information on when this happens but it seems to be a memory issue with JSNode.

[New LWP 7465]
[New LWP 7467]
[New LWP 7477]
[New LWP 7534]
[New LWP 7473]
[New LWP 7466]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
warning: the debug information found in "/var/cache/abrt-di/usr/lib/debug//lib64/libc-2.14.90.so.debug" does not match "/lib64/libc.so.6" (CRC mismatch).

warning: the debug information found in "/var/cache/abrt-di/usr/lib/debug/lib64/libc-2.14.90.so.debug" does not match "/lib64/libc.so.6" (CRC mismatch).

Core was generated by `anjuta'.
Program terminated with signal 11, Segmentation fault.

+ Trace 229160

Thread 3 (Thread 0x7fea1f0ee700 (LWP 7477))

  • #0 read
    at ../sysdeps/unix/syscall-template.S line 82
  • #1 read
    at /usr/include/bits/unistd.h line 45
  • #2 unix_signal_helper_thread
    at gmain.c line 4551
  • #3 g_thread_create_proxy
    at gthread.c line 1962
  • #4 start_thread
    at pthread_create.c line 309
  • #5 clone
    from /lib64/libc.so.6 






Comment 1


Johannes Schmid





          2011-11-30 18:55:00 UTC
        



http://git.gnome.org/browse/anjuta/commit/?id=4b41d02658a6dc07dc1216a74e424984a0563ee7

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.