Crash, error message on exiting stellarium

[barrykgerdes]

When exiting stellarium after certain actions have been performed during a stellarium session I get a "Windows" stellarium.exe application error-
The instruction at "0x6a2555d8" reference memory "0x00000050". The memory could not be "read"

As far as I can acertain this only happens after a search with a following zoom. There is no actual crash of stellarium. The message just comes up after a normal closure of stellarium if this action has been used at any time during a stellarium session. It is not critical. Just annoying. There is no corresponding entry in the log.txt file

The problem has been around for some time but I have generally ignored it as it hasn't affected other actions of stellarium.

It could be related to bug 526186

[faluco (borja-ferav)]

I'm able to reproduce this crash aswell. As mentioned by OP, search for some object and zoom at it, then close stellarium.
I've attached stellarium to the debugger to see the call stack and this is what it shows:
> QtCore4.dll!6a2555d8()
  [Frames below may be incorrect and/or missing, no symbols loaded for QtCore4.dll]
  msvcrt.dll!77bfc774()
  QtCore4.dll!6a2dca89()
  msvcrt.dll!77bfc2e3()
  QtCore4.dll!6a213a7b()
  QtCore4.dll!6a215138()
  libstelMain.dll!6729d5a7()
  msvcrt.dll!77c10e66()
  libstelMain.dll!6729d645()

The crash happens at the same addres as OP's:
6A2555D8 8B 40 50 mov eax,dword ptr [eax+50h]
eax is 0, so it's trying to read an invalid memory address.

[Fabien Chéreau (xalioth)]

I cannot reproduce that. On which platform does this happen?

[barrykgerdes (barrygastro)]

Hi Fabien

It happens in Windows XP SP3 pentium 4 3GHz. It does not happen all the time but I am able to reproduce it by starting the program then zooming in on an object then close the program. However sometimes I have started stellarium and run for some time doing various functions and closure has not produced the error.

A similar error occured some time ago when I used to load the dynamic satellite module and I gather it was something to do with the internet requests for updates (maybe not exiting the internet).

Barry Gerdes
Beaumont Hills Observatory
S 33' 41' 44" E 150' 56' 32"

> Date: Thu, 25 Mar 2010 14:58:25 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 534674] Re: Crash, error message on exiting stellarium
>
> I cannot reproduce that. On which platform does this happen?
>
> ** Changed in: stellarium
> Importance: Undecided => Low
>
> --
> Crash, error message on exiting stellarium
> https://bugs.launchpad.net/bugs/534674
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Looking for a new home? With all the latest places, searching has never been easier.
http://clk.atdmt.com/NMN/go/157631292/direct/01/

[faluco (borja-ferav)]

I'm running windows xp SP3 as well. Try doing it just after opening stellarium, i'm able to reproduce it every time i do it this way.

[Tom (tom-mills9)]

I have had the same problem when closing stellarium has not affected the program itself starts back up fine without reboot of computer, i am running windows xp pro sp3 pentium 4 ati mobility radeon x600 graphics card. Still having problems with font on bottom control bar being unreadable.

[faluco (borja-ferav)]

Fabien, this is the call stack QtCreator is showing when it crashes, i hope this one is more useful:

0 ZN9QIODevice5writeEPKcx C:\Qt\2010.01\qt\bin\QtCore4.dll 0 0x6a25521c
1 StelLogger::writeLog C:\prog\stellarium\builds\qtcreator-build\src\libstelMain.dll 0 0x6729e9ab
2 StelLogger::debugLogHandler C:\prog\stellarium\builds\qtcreator-build\src\libstelMain.dll 0 0x6729ea4d
3 Z17qt_message_output9QtMsgTypePKc C:\Qt\2010.01\qt\bin\QtCore4.dll 0 0x6a1cf990
4 Z17qt_message_output9QtMsgTypePKc C:\Qt\2010.01\qt\bin\QtCore4.dll 0 0x6a1cfb43
5 Z8qWarningPKcz C:\Qt\2010.01\qt\bin\QtCore4.dll 0 0x6a1cfcc2
6 ZN14QWaitConditionD1Ev C:\Qt\2010.01\qt\bin\QtCore4.dll 0 0x6a1d6f69
7 ZN17QFactoryInterfaceD1Ev C:\Qt\2010.01\qt\bin\QtCore4.dll 0 0x6a30eb03
8 ZN7QObjectD2Ev C:\Qt\2010.01\qt\bin\QtCore4.dll 0 0x6a2c5b5a
9 ZN9QHostInfo12setAddressesERK5QListI12QHostAddressE C:\Qt\2010.01\qt\bin\QtNetwork4.dll 0 0x6ff50615
10 ZN12QHostAddress11parseSubnetERK7QString C:\Qt\2010.01\qt\bin\QtNetwork4.dll 0 0x6ff4fe71
11 ?? C:\Qt\2010.01\qt\bin\QtNetwork4.dll 0 0x6ff0102f
12 ?? 0 0x00000000

[Bogdan Marinov (daggerstab)]

I made a debug build. Here's the log (crash after searching for an object):

0 QFlags<QIODevice::OpenModeFlag>::operator& qglobal.h 2188 0x6a2af3d9
1 QIODevice::write qiodevice.cpp 1265 0x6a1a967b
2 StelLogger::writeLog StelLogger.cpp 266 0x08e12891
3 StelLogger::debugLogHandler StelLogger.cpp 260 0x08e127fa
4 qt_message_output qglobal.cpp 2196 0x6a10e408
5 qt_message qglobal.cpp 2296 0x6a10e65a
6 qWarning qglobal.cpp 2378 0x6a10e6e1
7 ~QWaitCondition qwaitcondition_win.cpp 155 0x6a115dd4
8 ~QThreadPoolPrivate qthreadpool_p.h 69 0x6a264af1
9 QScopedPointerDeleter<QObjectData>::cleanup qscopedpointer.h 62 0x6a267efe
10 ~QScopedPointer qscopedpointer.h 100 0x6a25e701
11 ~QObject qobject.cpp 992 0x6a20cfd0
12 ~QThreadPool qthreadpool.cpp 430 0x6a10d872
13 ~QHostInfoLookupManager qhostinfo.cpp 454 0x0c591b64
14 ~QGlobalStaticDeleter qglobal.h 1799 0x0c5d86b7
15 __tcf_0 qhostinfo.cpp 64 0x0c590b72
16 __dll_exit D:\Qt\2010.02.1\qt\bin\QtNetworkd4.dll 0 0x0c54102f
17 DllMainCRTStartup@12 D:\Qt\2010.02.1\qt\bin\QtNetworkd4.dll 0 0x0c5410f5
18 ntdll!LdrSetAppCompatDllRedirectionCallback C:\WINDOWS\system32\ntdll.dll 0 0x7c90118a
19 ?? 0 0x0c540000
20 ?? 0 0x00000000
... <More>

The number after the file name is a line number.

[Bogdan Marinov (daggerstab)]

I managed to fix the _crash_, but not the underlying issue. Now instead of crashing, Stellarium outputs a message in the console. ("QWaitCondition: Destroyed while threads are still waiting") I'm not sure what the issue is, something with the network connection. If someone wishes to pursue it, please open a new bug report.

The fix has been committed to Stellarium's code repository at SourceForge as revision 6056:
http://stellarium.svn.sourceforge.net/viewvc/stellarium?view=rev&revision=6056

What the fix does:
http://doc.trolltech.com/4.6/qtglobal.html#qInstallMsgHandler

[faluco (borja-ferav)]

Interesting, maybe the network connections aren't properly closed because you have to wait for the condition variable to free it and then close down the whole program.