Open GoogleCodeExporter opened 9 years ago
Same issue on x64 version.
Original comment by rockeet...@gmail.com
on 21 Aug 2012 at 6:28
the same issue on intel processor, please fix it asap
Original comment by milewsk...@gmail.com
on 23 Aug 2012 at 8:46
Are your sure you closed Miranda or just the contact list?
Can you try to run dbtool on you database and can you try with an clean
installation?
Original comment by hosteddinner
on 25 Aug 2012 at 11:02
On new installation it's no problem.
I made some tests and found that problem was with GG plugin (GaduGadu) and
newest miranda versions. After disable this plugin, miranda proces close
normally.
Original comment by przyby...@gmail.com
on 27 Aug 2012 at 8:26
Mine remains running after reporting a crash, which is described in details in
http://code.google.com/p/miranda/issues/detail?id=1607#c1)
Original comment by yurken...@gmail.com
on 27 Aug 2012 at 2:32
From my experience, Miranda does not terminate properly since 0.10.0.0 provided
the GG plugin has signed in at least once.
Original comment by robs.mai...@gmail.com
on 31 Aug 2012 at 9:14
I don't use GaduGadu (don't even have dll in Miranda/plugins) but still
experience "process remains after Exit" issue from time to time. Approximately
4 out of 5 times I exit Miranda.
Original comment by 2sa...@gmail.com
on 6 Sep 2012 at 12:10
There is a dead lock in gg/miranda. I made a quick look at the code. This is
what happens:
1. GG receive EV_PROTO_ONEXIT event.
2. GG is calling gg_uninitavatarrequestthread() which reset dwThreadId of
avatar request task (GG/Avatar).
3. GG is waiting for GG/Avatar to finish. This is infinite wait on main thread.
4. GG/Avatar happens to be in a middle of request and calls
DBWriteContactSettingByte()
5. DBWriteContactSettingByte() lead to call to NotifyEventHooks()
6. NotifyEventHooks() redirect call to main thread if it is called from other
one (this is the case)
7. NotifyEventHooks() waits for queued event to finish.
As a result main thread waits for GG to finish, GG waits for main thread to
handle an event.
Original comment by mich...@gmail.com
on 14 Sep 2012 at 10:24
Original comment by s...@miranda-im.org
on 19 Sep 2012 at 3:14
So, any resolution? I've never signed in to GG!
Original comment by paul.fur...@gmail.com
on 24 Sep 2012 at 5:18
I wish it to be easy. Problem is related to event queue.
I thought about putting whole GG instance in separate thread, but if I do
plugins need a more intelligent way to finalize themselves.
In UninitializeStaticAccounts() after calling OnEvent(EV_PROTO_ONREADYTOEXIT)
event queue should be processed until all protocols report they're ready to
exit.
Then will be safe to call OnEvent(EV_PROTO_ONREADYTOEXIT).
Should work assuming event queue will not block.
Original comment by mich...@gmail.com
on 26 Sep 2012 at 8:42
Sorry for the silence... I believe I will find time over the weekend to finally
settle this issue.
Original comment by dezred
on 26 Sep 2012 at 8:54
My miranda version is newest Miranda IM version: 0.10.4.0 Unicode and after
closing miranda system has problem with close too. During this closing it`s
shows the message " ending the program History++ Main window..."
¤ GG.dll v.[b]0.10.4.0[/b] [25 Sep 2012] - Gadu-Gadu Protocol
¤ historypp.dll v.[b]1.5.1.4[/b] [23 Feb 2010] - History++ (2in1)
Original comment by and.sobi...@gmail.com
on 26 Sep 2012 at 9:41
Attachments:
It seems to be solved with newest version miranda-im-v0.10.5.
Original comment by and.sobi...@gmail.com
on 21 Oct 2012 at 2:07
Sorry, the situation is nearly the same. Only one notice: only if Gadu-Gadu
account is not connected miranda process closes properly. Temporary solution :
disconnect Gadu-Gadu and then close Miranda.
Original comment by and.sobi...@gmail.com
on 21 Oct 2012 at 8:56
Original comment by dezred
on 6 Nov 2012 at 9:33
I just installed ver. 10.9.0 bug still exists. Database files are locked by
system, after choosing exit. I may provide log (if such exists) and more info
if needed. For me selecting Offline before close do not ends process.
Original comment by m...@smogura.eu
on 11 Dec 2012 at 2:30
Guys, it's really annoying... Is there any chance it will be fixed anytime
soon? 5 months is long enough to start looking for alternative to Miranda, I
guess...
Original comment by dro...@gmail.com
on 5 Jan 2013 at 9:14
Same here, I have to kill miranda process manually every time atfer closing
program
Original comment by thelag...@gmail.com
on 15 Feb 2013 at 10:41
Confirmed. Problem can be bypassed by disconnecting (ctrl+0) before quitting,
but that's tedious.
Original comment by leafn...@gmail.com
on 25 Mar 2013 at 12:03
Miranda 10.13.0 Unicode, used on Windows XP SP3 and Windows 7 SP1. The same
problem occurs. Although logging out from GG network helps it can't be treated
as a solution to this issue.
I've attached VesrionInfo file.
Original comment by pallan.l...@gmail.com
on 23 Jun 2013 at 10:12
Attachments:
please fix this or we will be forced to stop using Miranda ;(
Original comment by xyloh...@gmail.com
on 1 Jul 2013 at 5:08
Very annoying. Unable to start miranda - need to restart Windows. It should be
High priority, not medium!
Original comment by ra...@sygnital.pl
on 9 Aug 2013 at 4:11
Attachments:
You don't need to restart Windows. Just kill Miranda process from Task manager
and start Miranda.
Original comment by rafal.th...@gmail.com
on 12 Aug 2013 at 7:30
So that's a known issue.
Disconnecting GG works for me, but I'm not planning to do that...
Still no fix?
Original comment by mac...@grischke.net
on 21 Dec 2013 at 4:47
[deleted comment]
I got notification about a new comment in this topic and realized that I've
actually stopped using Miranda because of that problem. I was using it for at
least 5 years.
Original comment by ra...@sygnital.pl
on 22 Dec 2013 at 10:22
I moved to WTW about year ago, because of this issue. Now I came back with hope
that something changed but there is still no fix. In comment number #8 you can
find a reason why problem occurs.
Original comment by pbrom...@gmail.com
on 4 Feb 2014 at 5:25
Last non affected version of miranda is 0.9.52
Original comment by luk3...@gmail.com
on 9 Mar 2014 at 8:41
Original issue reported on code.google.com by
przyby...@gmail.com
on 21 Aug 2012 at 6:40