-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fifth crashes when JS is turned on for any webpage #31
Comments
For command outputs, please put them inside code blocks for readability (use three backticks before and after the text). Thank you for the report. Fifth has never supported Android, and is not expected to work. Something is badly wrong with both JS and FLTK - just popping up a window causing a crash is quite serious. I won't close the bug directly, but you're completely on your own for running it on Android. |
Hi! thanks for replying so fast.. I'm running fifth on an X11 environment on android.. so it's more or less a normal linux environment.. (i've also tried running it in a chroot jail and it still crashes there so there isn't any problem with paths). I just wanted to know whether this crash is related to webkit directly (so i would know where exactly i need support)? (also i built webkit on my phone itself and it took me about 2.5 hours.. so if it is indeed a webkitfltk problem, then i'll leave it at that and just use fifth with js turned off) Just a few minutes ago, i modified about.cpp and about:history and about:config work for my build. also, thanks for this project.. this is the best browser i have been able to build for my android x11 environment.. and i've been able to make it very portable too :) (sorry for the jumbled output.. i can't copy from the terminal with android's clipboard and retain the formatting for some reason, it ends up being two long lines) |
also, i had to comment out the lockfile mechanism (because the required functions are not present in android's bionic libc). will that cause any problems? otherwise, there were just a few minor changes i had to make here and there for the whole thing to work. I think those are trivial. |
Even an X11 Android env differs quite a bit from desktop Linux, in
Bionic libc, system paths, and a few other things. BTW are you using
touch to operate it? I would have thought the buttons too small etc for
using with a finger, everything was designed for a mouse.
The JS crash is webkit-side, but you won't be able to get support from
the webkit folks, as WebkitFLTK is not an officially supported port.
Most probably it tried to use some Android-specific path instead of the
Linux path that's been tested.
You may want to use the git versions of both, since the 0.5.x releases
are a bit old (well, the git versions are also old, but have a few
changes more).
Disabling the lockfile, then you won't have protection from
accidentally launching twice, which will lead to corruption in the
history/etc files.
|
i'm new to debugging things.. is there any way that gdb can specify the line number or the exact context in which the segfault got initiated.. i mean, it does show the function call but not the exact location, if that makes any sense.. I built TigerVNC's Xvnc server.. so it's just a vnc session with a mouse and all.. i'll have to take the risk with the lockfile because mkfifoat isn't available in android's api 21 :/ moreover, i'll try to investigate a bit further, but building webkit over and over is a pain (i built it on my phone because my pc isn't powerful enough..) (also, are there any important upgrades in the git version.. because i'm trying to stray away from building everything again.. or if i could patch existing source files so that i wouldn't have to build everything again) i finished making my changes and as of now fifth works really well except for the js part.. |
Gdb can show line numbers only if you built with -g. For webkit, that
will take a few gbs more space.
There's indeed a minimum window size set, and it's supposed to act like
that. It's a standard X feature, but maybe not often used in apps.
I don't remember what all changes are in git vs 0.5, you'll have to
check the git histories.
|
i checked the changes made in the git version.. most of them were todo-s, some curl errors, fltk image preview in dialog boxes and most importantly openssl-1.1 compatibility i think.. i know openssl-1.0.2 is eol.. i'll try to build with 1.1 again.. the other changes are related to things which will work only if js works.. so yeah.. i think my main incentive would be openssl-1.1 compatibility (which i can probably just patch in and rebuild) i also checked webkitfltk's git logs and i unknowingly made some of the patches too.. to mitigate build errors.. if you want, you can update the spoofed useragent to the latest firefox esr release.. i just did that :) thanks a lot for the help btw |
Could you please share some more information on what your environment is? It'd be useful to recreate your crashes. |
You can use my app (http://chiselapp.com/user/searemind/repository/xhaskell/home) on an Android ARM device to exactly replicate the environment.. it is just a terminal emulator for android running on toybox's coreutils implementation (https://jackpal.github.io/Android-Terminal-Emulator/) which i modified to include an X server (tigervnnc's VNC server) and then i access that display through a vnc viewer.. you can also recreate the environment by building Fifth using packages from an app called Termux (i built fifth for the first time using this.. and had to build a lot of libraries manually).. it might take a while though.. either way.. both of them are terminal emulators for non-rooted android devices.. i am not very well versed in debugging practices and i only checked the backtraces and function calls before the segfault.. which did not prove to be very informative since WebKit is HUGE.. |
I'm sorry if i do something wrong as this is my first time reporting a bug on any software ever..
also, clicking on the "History" and "Advanced Config" menu options result in an instant crash.
For this build, I built webkitfltk-0.5.1 for android using "-DNDEBUG" and "-D__ANDROID_API__=21" (for android 5 compatibility)
The text was updated successfully, but these errors were encountered: