Constant Crashing, Apparently Caused By Proxy Server

7 posts / 0 new
Last post

I apologise if this isn't allowed, but I posted this bug report on Github and it hasn't received a response, so I thought it might be better to paste it here. It is issue #950 on Github.

--------------------------------------------------------------------------

I'm using the latest version (0.18.4) on Windows 7 SP1 x64.

QuiteRSS crashes about 5 times a day, and it seems to be related to the proxy server I'm using. This is the latest error message from Windows:

QuiteRSS has stopped working

Problem signature:

Problem Event Name: APPCRASH
Application Name: QuiteRSS.exe
Application Version: 0.18.4.3674
Application Timestamp: 049ef4d0
Fault Module Name: Qt5Network.dll
Fault Module Version: 5.4.2.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 00019993
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

The debug file in the QuiteRSS directory shows a huge stream of the same proxy-related entries (I've edited out my username & proxy address)::

27.10.2016 09:28:39.084 WARNING: QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-socks5://my_usernameatproxy_address.com:1080'
27.10.2016 09:28:39.084 WARNING: QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-socks5://proxy_address.com:1080'

The debug file is almost entirely made up of the above entries. Occasionally, the following entry can be seen sandwiched between the others:

27.10.2016 09:28:39.623 WARNING: QNativeSocketEngine::read() was called not in QAbstractSocket::ConnectedState or QAbstractSocket::BoundState

Thanks for your time.

Try version 0.17.7

Try version 0.17.7

Quote: Try version 0.17.7

Quote:
Try version 0.17.7

As per your advice, I've been using version 0.17.7 for a few days without any crashes, so thank you for the tip!

Is this a known issue that will be addressed in the next update, or should I stick with 0.17.7 for the foreseeable future?

Thanks again!

Does the latest version (0.18

Does the latest version (0.18.5) fix this issue, or should I stick with 0.17.7?

Cheers!

You can try, but I think that

You can try, but I think that the problem is in libraries qt

I see that version 2 is being

I see that version 2 is being developed. Will this version depend on the same QT libraries that cause this bug?

 

Cheers!

No, will not be depend.

No, will not be depend. Therefore, we develop a new version