After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343167 - Crash when refreshing a file
Crash when refreshing a file
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
: 341820 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-05-28 10:12 UTC by Wouter Bolsterlee (uws)
Modified: 2006-05-29 15:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Wouter Bolsterlee (uws) 2006-05-28 10:12:03 UTC 
1. View a PDF file
2. Rebuild the PDF file (pdflatex in my case)
3. Refresh during writing: this results in an error (of course)
4. Dismiss the error
5. Refresh after the PDF file has been completely written (this should work again)
6. CRASH!


Backtrace was generated from '/opt/gnome/bin/evince'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1229445440 (LWP 2917)]
[New Thread -1232090192 (LWP 2918)]
0xb7273221 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 68495

Thread 2 (Thread -1232090192 (LWP 2918))

  • #0 pthread_cond_wait
    from /lib/tls/libpthread.so.0
  • #1 ev_render_thread
    at ev-job-queue.c line 171
  • #2 g_thread_create_proxy
    at gthread.c line 553
  • #3 start_thread
    from /lib/tls/libpthread.so.0
  • #4 clone
    from /lib/tls/libc.so.6 






Comment 1


Nickolay V. Shmyrev





          2006-05-28 11:03:48 UTC
        



Really so, thanks for catching this.






Comment 2


Nickolay V. Shmyrev





          2006-05-28 11:04:54 UTC
        



*** Bug 341820 has been marked as a duplicate of this bug. ***






Comment 3


Wouter Bolsterlee (uws)





          2006-05-28 11:52:35 UTC
        



Heh, I forgot I already filed the issue (cause was unknown at that time)... :)






Comment 4


Nickolay V. Shmyrev





          2006-05-29 15:35:12 UTC
        



Should be fixed now.