Skip to content
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

shared SQL database - jabref updates one char and crashes after #9787

Open
2 tasks done
Processeer opened this issue Apr 24, 2023 · 9 comments
Open
2 tasks done

shared SQL database - jabref updates one char and crashes after #9787

Processeer opened this issue Apr 24, 2023 · 9 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs shared-database

Comments

@Processeer
Copy link

JabRef version

Latest development branch build (please note build date below)

Operating system

Windows

Details on version and operating system

Windows 11 pro 64bit Version 22H2 Built 22621.1555

Checked with the latest development build

  • I made a backup of my libraries before testing the latest development version.
  • I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

SQL database is within an intranet, so from outside I have to connect via VPN

  1. Connecting to Intranet through Barracuda VPN ... ok
  2. connecting to shared database ... ok
  3. pulling data ... ok
  4. changing entries ... now it gets interesting
  • if I type a "," it is instantly changed in the database (checked via phpMyAdmin). It takes JabRef 5-10s to return focus to the user
  • If I type characters the first one is instantly updated into the database, jabref is frozen and nothing more happens in the database
  • If I paste an entire string or even an entire entry at once, this one is updated/ created but jabref does not come around. I can't read the log since its gone after restart. (is there an option to recover some kind of crash report? or last actions to derive from?)
  • I tried to insert a group - it does work without crash, database is updated, focus returned

This looks like a special thing to me. Since jabref can communicate with the database in general but somehow there is a disturbance after one UPDATE cycle.

Appendix

JabRef 5.10--2023-04-13--81f2688
Windows 11 10.0 amd64
Java 19.0.2
JavaFX 20+19

Log File
Paste an excerpt of your log file here
@ThiloteE
Copy link
Member

Might be related: #8977

@ThiloteE
Copy link
Member

What do you mean with

but jabref does not come around

Does it freeze too?

What version of sql are you using?

@Siedlerchr
Copy link
Member

refs #8496
It freezes/blocks because sync happens on the UI thread. Tried to fix this but caused deadlocks...
Regarding logs:

Q: Where can I find JabRef's log files?
A: On Windows, one finds the log files in %APPDATA%..\Local\org.jabref\jabref\Logs{version}. {version} indicates the currently used JabRef version.

@ThiloteE ThiloteE added shared-database bug Confirmed bugs or reports that are very likely to be bugs labels Apr 24, 2023
@github-project-automation github-project-automation bot moved this to Normal priority in Prioritization Apr 24, 2023
@Processeer
Copy link
Author

ya, "does not come around" means it freezes - looks like its waiting for some kind of response it does not get. But then Im am not a programmer and am not using programmer language :) sorry for that

SQL:: 10.3.29-MariaDB

@Processeer
Copy link
Author

I surely did not change that many things that needed saving in the log file. Maybe it tells you something.

log.txt

by the way: the foldes name is:
~ 5.10--2023-04-13--81f2688\

indicating the 13th April but the content is from the 24th April. Almost missed it.

@Processeer
Copy link
Author

following your lead with #8496

I deactivated the emodificationdate update:
grafik

and yes it does not crash anymore. It sometimes just takes some seconds to return th focus to the user.

@Siedlerchr
Copy link
Member

Glad to hear that this helps. I was on a good way with my PR, however in the end I did not manage to solve the deadlocks that now occured.:(

@Processeer
Copy link
Author

never give up! sometimes the next day everything seems so easy.

@Processeer
Copy link
Author

connected to #8485 too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs shared-database
Projects
Status: Normal priority
Development

No branches or pull requests

3 participants