gedit crashed with SIGSEGV in g_main_context_dispatch()

[SignedAdam]

Opened a big text file

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gedit 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1
Uname: Linux 3.8.0-9-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.9-0ubuntu2
Architecture: amd64
Date: Sun Mar 3 11:26:14 2013
ExecutablePath: /usr/bin/gedit
MarkForUpload: True
ProcCmdline: gedit /home/username/Downloads/DofusInstall.run
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x440a48: mov 0x10(%rax),%rdi
 PC (0x00440a48) ok
 source "0x10(%rax)" (0xaaaaaaaaaaaaaaba) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gedit crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 gnome-session[2017]: WARNING: Failed to start app: Unable to start application: Failed to execute child process "/usr/lib/tracker/tracker-miner-fs" (No such file or directory)
 gnome-session[2017]: WARNING: Failed to start app: Unable to start application: Failed to execute child process "/usr/lib/tracker/tracker-store" (No such file or directory)
 (gnome-settings-daemon:2100): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed
 (gnome-settings-daemon:2100): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed

[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 #1036621, 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.