[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: high cpu load with image loading
From: |
joakim |
Subject: |
Re: high cpu load with image loading |
Date: |
Wed, 01 Sep 2010 10:35:30 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
"Dirk-Jan C. Binnema" <address@hidden> writes:
> Hi,
>
> I'm using a fairly recent emacs (24.0.50.8), but when trying to load an image
> with
>
> (put-image (create-image "pic.jpg") 0) ;; some normal 1024x768 jpeg image
>
> I only get a little square, and emacs consumes ca. 60% cpu, with X taking a
> lot of the rest -- this continues for at least a minute or so. I checked with
> oprofile, I get the following profile (see below). So what is this
> assq_no_quit doing?
Could you possibly do a m-x report-emacs-bug ?
It would be nice to see your configure options etc.
Also provide a link to your image.
>
> Best wishes,
> Dirk.
>
>
> CPU: Core 2, speed 1601 MHz (estimated)
> Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit
> mask of 0x00 (Unhalted core cycles) count 100000
> samples % symbol name
> 135329 50.5676 assq_no_quit
> 25840 9.6555 mark_object
> 6252 2.3361 Fgarbage_collect
> 5389 2.0137 re_match_2_internal
> 4981 1.8612 Fbyte_code
> 3240 1.2107 oblookup
> 2623 0.9801 Fstring_equal
> 2038 0.7615 Fplist_get
> 1875 0.7006 lookup_char_property
> 1835 0.6857 readchar
> 1833 0.6849 hash_string_case_insensitive
> 1810 0.6763 re_search_2
> 1370 0.5119 mark_char_table
> 1359 0.5078 Fall_completions
> 1318 0.4925 append_glyph
> 1310 0.4895 read1
> 1305 0.4876 Ffuncall
> 1272 0.4753 mark_vectorlike
> 1190 0.4447 internal_equal
> 1143 0.4271 x_produce_glyphs
> 1065 0.3980 merge_face_vectors
> 1062 0.3968 casify_object
> 1048 0.3916 sxhash
> 1044 0.3901 Fcompare_strings
> 1001 0.3740 display_mode_element
> 972 0.3632 set_buffer_internal_1
> 958 0.3580 Fassq
> 899 0.3359 find_interval
> 894 0.3341 validate_interval_range
> 882 0.3296 readbyte_from_file
> 770 0.2877 specbind
> [...]
--
Joakim Verona
- Re: high cpu load with image loading,
joakim <=