Pages vues depuis 25/07/2007 : 25 261 089
Index du forum »» OS4 toutes plateformes confondues »» FE et "stability improvements". Sérieusement ?
Citation : zzd10hTiens, pour le pb de lags, un nouveau qui déclare ce problème--
AmigaONE X1000/1,8 Ghz (A-Eon), Radeon RX560, 2 Go de Ram et OS4.1 FE
Concernant les ralentissements, je ne sais pas si ça a un lien, mais durant l'un d'eux j'ai eu ça dans le Serial.
Après, je ne sais pas si ça correspond exactement à ce problème.
[elf] .eh_frame 0x51B8593C-0x51B85988 OS4_FE:Libs/xadmaster.library (sh_flags 0x 02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .hash 0x7F654000-0x7F6544CC OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .dynsym 0x7F6544CC-0x7F654FAC OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .dynstr 0x7F654FAC-0x7F65578A OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.data 0x7F65578C-0x7F6557A4 OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.dyn 0x7F6557A4-0x7F655B1C OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.plt 0x7F655B1C-0x7F655C9C OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .hash 0x7F656000-0x7F6564CC OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .dynsym 0x7F6564CC-0x7F656FAC OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .dynstr 0x7F656FAC-0x7F65778A OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.data 0x7F65778C-0x7F6577A4 OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.dyn 0x7F6577A4-0x7F657B1C OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.plt 0x7F657B1C-0x7F657C9C OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .hash 0x7F658000-0x7F6584CC OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .dynsym 0x7F6584CC-0x7F658FAC OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .dynstr 0x7F658FAC-0x7F65978A OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.data 0x7F65978C-0x7F6597A4 OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.dyn 0x7F6597A4-0x7F659B1C OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
[elf] .rela.plt 0x7F659B1C-0x7F659C9C OS4_FE:SObjs/libgcc.so (sh_flags 0x02)
has read-only flag in section header
but is located in a read-write section of the program header
(linker (script) error?)
Salut Guillaume
<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
C'est car la valeur FPS est calculé après 2 tour de vaches ce qui sur ton x1000 prend vraiment un certain temps :-P
Pour des valeurs bien plus précise on peut prendre Microbe3D/Demo-View , et sans tourner l'objet, regarder la valeur TPF (? time per frame ? en ms) mais il faut alors activer le menu ? test & debug ?/ ?FPS limit OFF ? sinon la vitesse est bridée par défaut à 10 fps maxi pour libérer le CPU
Typiquement dans ce cas sur la Sam440 avec data/partygirl/partygirl.obj j'obtiens TPF 65 ms soit environ 200 000 triangles / secondes
Pour info Cow3D sur un PowerBookG4 + Morphos arrive presque à 100 fps (!) et sur WinUAE-68k en rendu hard/OpenGL à 50-60 fps je crois
Alain
Crash en train de naviguer avec Odyssey
Dump of context at 0xDFA53BA0
Trap type: ISI exception
Machine State (raw): 0x100000004200B030
Machine State (verbose): [Hyper] [ExtInt on] [Super] [FPU on] [IAT on] [DAT on]
Instruction pointer: 0x00000000
Crashed process: AmiDock (0x5EBCD7E0)
ISI verbose error description: Instruction address not found in hash or BAT (page fault)
0: 022BA454 5B487C30 DFEFDFDF 6FEF37A0 51B72340 00001322 022BAC68 00000000
8: 6FFFE300 00000000 545EE2F2 00000000 00000000 5F4C6F04 0001869F 5B488400
16: 5B4883A0 5B4883A4 5EBCD7E0 5B8DED00 02814948 5B487C90 00000000 5EBCD874
24: 00000000 02B30000 59C9CC64 00000000 59C9CC08 5FB59248 6FEF37A0 566E80D8
CR: 59335C99 XER: A000007E CTR: 00000000 LR: 022B9FFC
FP0 : FFF8000082004000 FF000000FF000000 0000000000000000 FF57341FFF593823
FP4 : FF583922FF573923 FF583924FF5A3B22 FF000000FF000000 FF000000FF000000
FP8 : 406EE00000000000 4060400000000000 4000000000000000 405D400000000000
FP12: 4330000080000000 4069400000000000 0000000000000000 0000000000000000
FP16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP28: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPSCR: 82004000
HID0: 0x8000000000000000 HID1: 0x000000005CE993B1
HID4: 0x4400240000080180 HID5: 0x0000006600000080
V0 : 00000000000000000000000000000000 FF000000FF000000FF000000FF000000
V2 : 3BC43BC43BC43BC43BC43BC43BC43BC4 00000000000000000000000000000000
V4 : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 3CC43CC43CC43CC43CC43CC43CC43CC4
V6 : 00FF3BC400FF3BC400FF3BC400FF3BC4 00000000010101010202020203030303
V8 : 3BC43BC43BC43BC43BC43BC43BC43BC4 3CC43CC43CC43CC43CC43CC43CC43CC4
V10: 013C3C3C013C3C3C013C3C3C013C3C3C 00000000000000000000000000000000
V12: 00FF3BC400FF3BC400FF3BC400FF3BC4 FF000000FF000000FF000000FF000000
V14: 001002120414061608180A1A0C1C0E1E 01000100010001000100010001000100
V16: FF3C3C3CFF3C3C3CFF3C3C3CFF3C3C3C 013C3C3C013C3C3C013C3C3C013C3C3C
V18: 00000000000000000000000000000000 01FF3CC401FF3CC401FF3CC401FF3CC4
V20: 00000000000000000000000000000000 00000000000000000000000000000000
V22: 00000000000000000000000000000000 00010001000100010001000100010001
V24: 00080109020A030B040C050D060E070F 00000010000000100000001000000010
V26: 0000000A0000000A0000000A0000000A 00050005000500050005000500050005
V28: 053D055A059E058A059B05C905C005BA 00050005000500050005000500050005
V30: 00050005000500050005000500050005 00140014001400140014001400140014
VSCR: 00000000 VRSAVE: 00000000
Disassembly of crash site:
il n'y a rien ensuite, même le Serial s'est stoppé avant de finir.
Citation : zzd10h
Merci les gars@ElwoodMerci mais dans ta description de BZ, il y a 2 incidents distincts1) New Text file qui crash avec ou sans MUNGECe bug a déjà été reporté par DaveBraco je pense.