Crashes immediately on macOS x86_x64 (solution inside) #10716
Labels
platform: macos
status: depends-on-external
A bug or issue that depends on an update of an external library
Milestone
Comments
|
It could be caused by the upgrade to JavaFX 21 but as far as I know that only affects Mac OS 10 and before. Cc @Siedlerchr. |
|
@tue87606 Do you have an m1/m2 system? Then please try the arm64 variant. I had issues with the x86_x64 variant as well on my m1 system. Seems to be coming from jfxwebkit Edit Seems to be coming from jfx21.0.1 and will be fixed by 21.0.2 might be related to openjdk/jfx21u@55ac7f0 |
|
This problem appears on the recently one month's build version. I am sure the version dated on Nov 23 have the problem. |
koppor
added
the
status: depends-on-external
|
@tue87606 and @iTao8 Could you try the build at https://builds.jabref.org/pull/10725/merge? (I know, it is not signed, but it should be executable nevertheless) |
|
@koppor the issue is not solved, even if I right click on an entry. |
|
@koppor I said the version dated on Nov 23 had the problem, but the version dated on Nov 3 is ok. Could you check the javafx versions of this two builds? |
|
JavaFX upgrade to 21 was committed on Nov. 7. |
Thank you for the Feedback. Thus, even the update to the latest JavaFX early access version is broken 🙈 |
We do not archive the builds, but the about dialog shows the JavaFX versions, which you IMHO stated - and we already know that JavaFX 21 is broken (and 22-ea, too). Thus, we need to downgrade. |
|
@tue87606 @iTao8 Can you test this version? https://builds.jabref.org/pull/10726/merge For me it worked and no longer crashed (but I am stil using ventura) |
|
The arm64 version (for m1/m2)macs works fine:; JabRef 5.12--2023-12-24--4233bad and for comparison works: |
This version works well. JabRef 5.13-PullRequest10726.11--2023-12-26--ed60503 |
Siedlerchr
changed the title
|
Fix has been integrated into the latest development version (main) |
|
still same problem with 5.12 on: |
|
@Finebouche Could you try the build of today? https://builds.jabref.org/main/ |
Does not crash, but using any text input field yields. |
|
@jfregin Do you have on screen keyboard or something related activated? Which OSX version are you using? |
|
@Siedlerchr OSX: 14.2.1 (23C71). Good catch with the keyboard, I indeed always keep the keyboard in the "hot corner". Error does not occur without. So that's a different issue. Sorry for causing confusion. |
|
I guess the bug with the keyboard is related to this one https://bugs.openjdk.org/browse/JDK-8235989 |
No, still crashing |
|
@Finebouche Could you show as the version using the about dialog? We need to be sure that the most recent version is used. Just as double check. -- Which Mac do you have? M1, M2, ...? |
|
My absolute bad @koppor, I had downloaded the wrong version. The new version (5.13) is stable (mac M2 ultra). thank you ! |
|
@Finebouche This is good news 😅. Thus, one step more towards the next release! |
|
Hi - I still experience JabRef crashing on startup on MacOS 12.6 (Monterey) and X86_64 arch. Crash log below. This is with the stable release and the latest nightly (2024-03-05). JabRef 5.11 (stable) seems to work without issues. |
|
@koppor - Re the javafxreproducer:
|
|
@chhei Just a double check: You do NOT run Mac OS 14.4, but an earlier version? |
|
Please try the binaries we already build with the new javafx https://builds.jabref.org/jdk-ea/ because gradle does not work out of the box with newer java versions |
|
@Siedlerchr The context was to try our JavaFX MWE @chhei Please output |
|
@chhei Sorry for the inconvenience. You can try the branch |
Correct - am on MacOS Monterey, v12.6 |
@Siedlerchr : The settings were based on @koppor 's earlier suggestion to try to compile with java 22/23. I then ran Tried out the new branch - crash report: javafxreproducer.log Terminal output: |
@Siedlerchr: Tried the version with jdk22-javafx23-ea+3 - same issue: crash on startup. Log: |
|
Thanks for all the info, I now will create a bug report at Oracle /openJdk Thanks again for testing all the variants and the patience! It will take a couple of days until I hear back from Oracle. |
Well, I think I have to thank you developers to look into this and for maintaining JabRef. Testing and reporting is only a small contribution and return for the open source effort you guys put in. |
2 tasks
2 tasks
|
Can you please test the latest development version? We just upgraded JavaFX and at least here on my M1 I can run the x86 app as well without problems |
|
@Siedlerchr - sorry for the delay! Happy to test/try out different options & again thanks for looking into this! |
[...] Commenting on my own remark - I'll test JabRef 5.13 and dev on other Macs I have access to and report back. Might be that this is something which is related to my setup, if there are no other reports from users who have similar issues. |
|
@chhei Would it be possible to test running from source ? |
|
@Siedlerchr - yes will try and compile from source again. I have just tested running JabRef 5.13 on a MacBook, Intel, MacOS Monterey 12.6 (similar to what I have) - works without issues (no extensive testing, but all seems to behave). I suspect that there is something peculiar on my machine that leads to the crash - maybe some older stray Java versions or settings, not sure. Any pointers of where such Java remnants are usually stored would be appreciated. |
|
The only thing I saw was something related to font loading from |
|
Wenn das Leben immer so einfach waere... @Siedlerchr! You're a legend. Resetting my font settings fixed all the troubles and I can now happily run JabRef 5.14/dev without issues. 
Thanks @Siedlerchr, @koppor for all the help looking into this. |
|
Yeahaw great to hear that it's solved now
Christian Heine ***@***.***> schrieb am Fr., 26. Apr. 2024,
20:34:
… Wenn das Leben immer so einfach waere... @Siedlerchr
<https://github.com/Siedlerchr>! You're a legend. Resetting my font
settings fixed all the troubles and I can now happily run JabRef 5.14/dev
without issues.
5-14.png (view on web)
<https://github.com/JabRef/jabref/assets/4818368/ec06da09-0820-482d-985d-142139c2547e>
Thanks @Siedlerchr <https://github.com/Siedlerchr>, @koppor
<https://github.com/koppor> for all the help looking into this.
—
Reply to this email directly, view it on GitHub
<#10716 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACOFZCDDI3IH5GKTKWPTXTY7KM3DAVCNFSM6AAAAABBBYBV7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZZHEZDSOBQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thanks again for your patience and continuous testing. I closed the issue now. : |
|
@Siedlerchr Should we file a JDK bug? OK, we should know from @chhei which font setting he had before... |
Gents - took a while, but: done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JabRef version
Latest development branch build (please note build date below)
Operating system
macOS
Details on version and operating system
Mac OS X 14.2.1
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
JabRef 5.12--2023-12-24--4233bad
Mac OS X 14.2.1 x86_64
Java 21.0.1
JavaFX 21.0.1+6
Thanks for your help! It would be much appreciated.
Appendix
...
Log File
The text was updated successfully, but these errors were encountered: