gjs-console crashed with SIGSEGV in JS_GetClass()

[Perfecto]

Nothing more

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gjs 1.39.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Apr 5 13:52:53 2014
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2013-09-14 (203 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
ProcCmdline: /usr/bin/gjs /usr/share/org.gnome.Weather.Application/org.gnome.Weather.Application
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=es_ES.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fd93cb82000 <_Z11JS_GetClassP8JSObject>: mov 0x8(%rdi),%rax
 PC (0x7fd93cb82000) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gjs
StacktraceTop:
 JS_GetClass(JSObject*) () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
 gjs_object_from_g_object () from /usr/lib/libgjs.so.0
 gjs_value_from_g_argument () from /usr/lib/libgjs.so.0
 ?? () from /usr/lib/libgjs.so.0
 ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: gjs-console crashed with SIGSEGV in JS_GetClass()
UpgradeStatus: Upgraded to trusty on 2014-03-24 (11 days ago)
UserGroups: adm audio avahi avahi-autoipd backup bluetooth bumblebee cdrom crontab dialout dip disk fax floppy fuse games list lp lpadmin mail netdev ntp pcscd plugdev sambashare saned scanner src sudo tape tty users video voice

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1281391, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.