QMutex::lock: Deadlock detected in thread -1537242400

[Jürgen Heinemann (Undefined)]

QBitttorent hang on startup with Message after Upgrading from qt 4.6.2 to 4.6.3:
QMutex::lock: Deadlock detected in thread -1537242400

Qt4 4.6.3
libtorrent-rasterbar 0.15.0

[Christophe Dumez (hydr0g3n)]

Did you rebuild qBittorrent after the Qt update?

Most qBT developers are using Qt 4.6.3 now and nobody experienced it yet (may be due to some non-default settings though)

[Christophe Dumez (hydr0g3n)]

Please check config file at ~/.config/qBittorrent/qBittorrent.conf

Look for
Connection\ResolvePeerHostNames=true

and switch it to false.

See if it changes the issue. I have checked my code and Peer Host name resolution is the only place where I use QMutex.

[Jürgen Heinemann (Undefined) (juergen-heinemann)]

> Did you rebuild qBittorrent after the Qt update?
Yes - i have rebuild qbittorent and libtorrent

> Connection\ResolvePeerHostNames=false
No effect :-(

PS My System Profile:
Linux 2.6.34 #1 ... i686 athlon i386 GNU/Linux LFS
gcc 4.4.4
boost 1.40.0
libtorrent-rasterbar 0.15.0
qt4 4.6.3

[Christophe Dumez (hydr0g3n)]

I need to make sure the problem does not occur because of some non-default setting.

Could you please move the config file out of the way and try again?

mv ~/.config/qBittorrent./qBittorrent.conf ~/.config/qBittorrent./qBittorrent.conf.bak

[Jürgen Heinemann (Undefined) (juergen-heinemann)]

OK - Now i have a little bit time to show your code.
It is not a good Idea to Initial QSettings before Q*Application was set.
Why? QSettings read Application Environments and set missed Data to Settings.
For Example see my Application XHTMLDBG Code at http://gitweb.hjcms.de/cgi-bin/index.cgi/xhtmldbg/tree/src/xhtmldbgmain.cpp?id=xhtmldbg-0.8.6.rc6

PS: Thanks for QBittorrent it's my favorite Torrent Client ;-)

[Christophe Dumez (hydr0g3n)]

Thanks.

It was actually already fixed in SVN for v2.2.9. It is probably the reason why I could not reproduce.