Opera closes very slowly (profilinglog)

Hi
Sorry if problem was mentioned before, but I found no threads about it.
Opera 11.51 on Windows XP 32 bit utilised for several days without closing (2-3 windows, 20-30 pages opened in each) is closing very slowly. Windows closes immediately but process stays for a long time.
Selected lines from profilinglog:

2011-10-27 08:52:46.112 -- Shutdown sequence starting
2011-10-27 08:54:01.992 4429 ms - Destructed managers
2011-10-27 08:54:04.649 442 ms - + thumbnails
2011-10-27 08:54:05.291 575 ms - + history
2011-10-27 08:54:06.620 1081 ms - + bookmarks
2011-10-27 08:54:08.598 1756 ms - + gadgets
2011-10-27 08:54:19.437 10732 ms - + ns4plugins
2011-10-27 08:55:37.740 78183 ms - + ecmascript
2011-10-27 08:55:39.461 1552 ms - + widgets
2011-10-27 08:57:57.575 137866 ms - + url
2011-10-27 08:57:58.767 234571 ms - Destroying core completed

The main problem is with ecmascript and url. Why it takes so long to destroy? Will it be fixed? 6 minutes is rather too much for closing a program on a dual core machine...
It happened to be much longer (20 minutes) but I had no log of it. Why? Because Opera after restarting (because of an exception) does not use command line options it had before (at least the profilinglog one). I suppose it's wrong.

Originally posted by Miroo75:

Opera 11.51 on Windows XP 32 bit utilised for several days without closing

I found this thread — I am sure that there are many others. A common factor seems to be leaving Opera running for a long time.

Are you starting from a saved session, or continuing from last time?

You could try saving the session, and Start with speed dial. Then load the session.

Originally posted by Pesala:

Are you starting from a saved session, or continuing from last time?

You could try saving the session, and Start with speed dial. Then load the session.

I'm starting with "continue from last time" option set on. I will try what you said next week, unfortunately it will take some time
But even if this works it is not the real solution. I'm wondering what opera does then and what the difference it would make when instead of slowly freeing the memory opera would Halt() or just kill the process.

I wonder how big your opera.win session file is? Mine is 10 K and 459 lines.

Originally posted by Pesala:

I wonder how big your opera.win session file is? Mine is 10 K and 459 lines.

If you mean autosave.win currently it's 95kB, 5000 lines.
opera.win is not used (modified in may 2007)

New data after 3 days of continuous work, opera opened empty and then loaded previously saved session, memory use: 1.6 GB. As usually most of the time took "ecmascript" and "url". It passed over half a minute from clicking close to start logging first item after "Shutdown sequence starting". there is definitely something to be fixed.

2011-11-04 14:24:01.796 -- Shutdown sequence starting
2011-11-04 14:24:38.762  83 ms - +++ Destructed Lexicon
2011-11-04 14:24:38.791  13 ms - +++ Closing indexer table
2011-11-04 14:24:38.791 124 ms - ++ Destructed MessageEngine - phase 1
2011-11-04 14:24:38.894 104 ms - +++ Prefs saved to index.ini
2011-11-04 14:24:38.919 128 ms - ++ Destructed Indexer
2011-11-04 14:24:39.013  94 ms - ++ Destructed AccountManager
2011-11-04 14:24:39.013   0 ms - ++ Destructed MessageEngine - phase 2
2011-11-04 14:24:39.060  47 ms - ++ Destructed Store
2011-11-04 14:24:39.060 395 ms - + Destructed MessageEngine
2011-11-04 14:24:39.916 2346 ms - Destructed managers
2011-11-04 14:24:39.918   2 ms - Committed prefs
2011-11-04 14:24:39.978 -- Destroying core starting
2011-11-04 14:24:39.998  11 ms - + webserver
2011-11-04 14:24:39.998   0 ms - + webp
2011-11-04 14:24:40.013  15 ms - + upnp
2011-11-04 14:24:40.013   0 ms - + upload
2011-11-04 14:24:40.013   0 ms - + updaters
2011-11-04 14:24:40.013   0 ms - + unicode
2011-11-04 14:24:40.429 416 ms - + thumbnails
2011-11-04 14:24:40.429   0 ms - + sqlite
2011-11-04 14:24:40.429   0 ms - + spellchecker
2011-11-04 14:24:40.429   0 ms - + rootstore
2011-11-04 14:24:40.429   0 ms - + prefsloader
2011-11-04 14:24:40.430   0 ms - + opera_auth
2011-11-04 14:24:40.430   0 ms - + obml_comm
2011-11-04 14:24:40.430   0 ms - + mime
2011-11-04 14:24:40.430   0 ms - + memory
2011-11-04 14:24:40.449  19 ms - + media_backends
2011-11-04 14:24:40.449   0 ms - + inputmanager
2011-11-04 14:24:40.449   0 ms - + idna
2011-11-04 14:24:40.768 319 ms - + history
2011-11-04 14:24:40.768   0 ms - + geolocation
2011-11-04 14:24:40.768   0 ms - + desktop_pi
2011-11-04 14:24:41.000 231 ms - + database
2011-11-04 14:24:41.000   1 ms - + content_filter
2011-11-04 14:24:41.411 411 ms - + bookmarks
2011-11-04 14:24:41.411   0 ms - + auth
2011-11-04 14:24:41.460  49 ms - + applicationcache
2011-11-04 14:24:41.460   0 ms - + about
2011-11-04 14:24:42.739 1279 ms - + gadgets
2011-11-04 14:24:42.783  44 ms - + security_manager
2011-11-04 14:24:42.783   0 ms - + webfeeds
2011-11-04 14:24:42.797  14 ms - + desktop_util
2011-11-04 14:24:42.797   0 ms - + scope
2011-11-04 14:24:42.797   0 ms - + search_engine
2011-11-04 14:24:42.797   0 ms - + svg
2011-11-04 14:24:42.797   0 ms - + xmlutils
2011-11-04 14:24:42.797   0 ms - + xpath
2011-11-04 14:24:42.797   0 ms - + zlib
2011-11-04 14:24:42.797   0 ms - + memtools
2011-11-04 14:24:42.819  21 ms - + wand
2011-11-04 14:24:42.819   1 ms - + sync
2011-11-04 14:24:42.819   0 ms - + doc
2011-11-04 14:24:42.819   0 ms - + datastream
2011-11-04 14:24:42.819   0 ms - + autoproxy
2011-11-04 14:24:51.308 8489 ms - + ns4plugins
2011-11-04 14:24:51.308   0 ms - + ecmascript_utils
2011-11-04 14:24:51.423 115 ms - + dom
2011-11-04 14:26:09.571 78140 ms - + ecmascript
2011-11-04 14:26:09.571   0 ms - + media
2011-11-04 14:26:09.571   0 ms - + forms
2011-11-04 14:26:09.571   0 ms - + dochand
2011-11-04 14:26:09.839 269 ms - + style
2011-11-04 14:26:09.841   1 ms - + windowcommander
2011-11-04 14:26:12.398 2558 ms - + widgets
2011-11-04 14:26:13.245 846 ms - + skin
2011-11-04 14:26:13.245   0 ms - + socks
2011-11-04 14:28:26.093 132862 ms - + url
2011-11-04 14:28:26.096   3 ms - + libssl
2011-11-04 14:28:26.097   0 ms - + libcrypto
2011-11-04 14:28:26.097   0 ms - + libopeay
2011-11-04 14:28:26.097   0 ms - + formats
2011-11-04 14:28:26.098   1 ms - + viewers
2011-11-04 14:28:26.626 529 ms - + softcore
2011-11-04 14:28:26.627   1 ms - + layout
2011-11-04 14:28:26.659  32 ms - + logdoc
2011-11-04 14:28:26.660   0 ms - + img
2011-11-04 14:28:26.663   3 ms - + console
2011-11-04 14:28:26.663   0 ms - + locale
2011-11-04 14:28:26.663   0 ms - + prefs
2011-11-04 14:28:26.664   0 ms - + prefsfile
2011-11-04 14:28:26.922 258 ms - + display
2011-11-04 14:28:26.922   0 ms - + encodings
2011-11-04 14:28:26.922   0 ms - + libvega
2011-11-04 14:28:26.922   0 ms - + util
2011-11-04 14:28:26.941  19 ms - + pi
2011-11-04 14:28:26.941   0 ms - + libgogi
2011-11-04 14:28:26.943 226961 ms - Destroying core completed

Originally posted by Miroo75:

I found no threads about it

There are indeed many threads about this. It's a longstanding, well-known but not well-understood problem with both slow shutdowns and failed shutdowns. My impression is that the failed shutdowns are probably the least understood, but the more common experience (and all of my experience) seems to be the slow shutdowns.

For an overview, see this post, this thread, this thread (notice the log snippet with long reported URL time), and some detailed observations in this thread; and it may be worthwhile following up on some of the other links mentioned in those threads.

There is also some worthwhile background info in this lengthy opera won't shut down thread, but 3 issues are comingled in the thread:

(1) slow shutdowns
(2) failed shutdowns (probably more info in this thread than any others as I recall)
(3) Opera minimized to system tray (unrecognized by the user)

Near the end of the thread, nearasfar reported better shutdown results from using the Exit option in Opera's Menu (Menu > Exit, File > Exit, or Alt+F+x) rather than Alt+F4 or the red Windows X. I don't know if there is anything to that, but I've since mentioned it in a couple of other threads (e.g., this post in one of the threads mentioned above, and at least a couple of other users have also reported improved shutdowns with that method.

Not many other users have reported Startup and shutdown profiling results, but since you've already been doing some logging , you might find this thread helpful, and there is a bit of logging info about slow startups in this thread. A forum search for "profiling" with my username will turn up several other threads, but I've been away from the whole issue (and away from the Opera forums) for about 6 months now, and I can't recall right now if any of them have any log details.

It was a very interesting issue for me for a while, but since I stopped logging and was away away from the forums for so long, I'm a little fuzzy on some of the details now. I don't think I have anything new to offer at this point, but I'd be glad to compare notes/observations (though I'll probably have to work a bit to get back up to speed). ...And if comparing logs logs would be helpful, I kept all the ones I did back then.

Edit: I think one of the first threads I mentioned above has a couple things to try that might make a difference (deleting cache files and cache4 index, fresh Opera installation, etc.) and I forgot to mention that above, but don't have time now to go back and check which it was.