Bug 340977 - [qtruby]Qt::WebView crashed due to threading issues (with confirmed fixes in qtbindings)
Summary: [qtruby]Qt::WebView crashed due to threading issues (with confirmed fixes in ...
Status: RESOLVED UPSTREAM
Alias: None
Product: bindings
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kde-bindings
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-15 06:59 UTC by margueritesu
Modified: 2018-11-18 11:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
full error log (79.33 KB, text/plain)
2014-11-15 06:59 UTC, margueritesu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description margueritesu 2014-11-15 06:59:27 UTC
Created attachment 89591 [details]
full error log

Hi,

My ruby version is 2.1.4 and qtruby version 4.14.3. (latest I think)

When I ran a sample script like this:

#!/usr/bin/ruby
require 'Qt'
require 'qtwebkit'

app = Qt::Application.new(ARGV)
web = Qt::WebView.new
web.load Qt::Url.new('http://www.baidu.com/')
web.resize 1024, 640
web.show
app.exec

it crashed randomly (sometimes crash at startup, sometime crash after clicking one or two links)

The error output is (part of, it's too long for one comment):

/usr/lib64/ruby/site_ruby/2.1.0/Qt/qtruby4.rb:469: [BUG] vm_call0_cfunc_with_frame: cfp consistency error
ruby 2.1.4p265 (2014-10-27 revision 48166) [x86_64-linux-gnu]

-- Control frame information -----------------------------------------------
c:0005 p:---- s:0015 e:000014 CFUNC  :respond_to_missing?
c:0004 p:---- s:0013 e:000012 CFUNC  :method_missing
c:0003 p:0009 s:0009 e:000008 METHOD /usr/lib64/ruby/site_ruby/2.1.0/Qt/qtruby4.rb:469
c:0002 p:0097 s:0006 E:0012a8 EVAL   ./test_Webview.rb:10 [FINISH]
c:0001 p:0000 s:0002 E:002408 TOP    [FINISH]

-- Ruby level backtrace information ----------------------------------------
./test_Webview.rb:10:in `<main>'
/usr/lib64/ruby/site_ruby/2.1.0/Qt/qtruby4.rb:469:in `exec'
/usr/lib64/ruby/site_ruby/2.1.0/Qt/qtruby4.rb:469:in `method_missing'
/usr/lib64/ruby/site_ruby/2.1.0/Qt/qtruby4.rb:469:in `respond_to_missing?'

This is the same behaviour as https://github.com/ryanmelt/qtbindings/issues/51 describes.

Its comments indicates that this is a threading issue and qtbindings after 4.8.5.1 (it follows Qt version) doesn't have this problem.

I think these commits might help:

https://github.com/ryanmelt/qtbindings/commit/ffb3c6a664ba9cfb30e7f5fd1cbcb63212880d1a#diff-8

https://github.com/ryanmelt/qtbindings/commit/40deaa0cb3cfe99b43eca2c52cfc2a0c9aa63f2f

But they mixed stuff in one commits, so I'm not able to tell which codes resolved the issue or even provide a patch.

Can you please take a look at this and port this into qtruby? (the fix exists for 11 months, so I think it's pretty stable)

Thanks

Marguerite
Comment 1 Andrew Crouthamel 2018-10-31 03:57:31 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Bug Janitor Service 2018-11-15 10:49:39 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 margueritesu 2018-11-18 11:00:55 UTC
more like a ruby bug: https://bugs.ruby-lang.org/issues/11903