Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: seeking bug in 0.7.7 in mp3s (Read 4540 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

seeking bug in 0.7.7 in mp3s

Since upgrading to 0.7.7, after seeking an mp3 about 3 or 4 times (in the forward direction) foobar crashes. I've tested this with a few different mp3s, encoded with different encoders as well. I have 512 of ram and a p4 2.66ghz notebook, so the hardware doesn't seem to be the problem. I wonder if anyone else is having this problem besides me.

seeking bug in 0.7.7 in mp3s

Reply #1 –
I have the Same Problem ....... It will only happens if you Seek without a Pause three ore more times ..... I have noticed that this Problem every Times come if the Spectrometer (the Long one in the Main Window) doesnt refreshed (if the Musik Plays and the window is clear). If you wait until the spectrum comes back and you seek again you´ll see, that Foobar doesnt crash or Freezed

This is not a Solution (i know) but its a way *gg*

Greets
OUTLiNE

By the Way .... Sorry for my bad English  (Its a long time ago since i was in school) *gg*

Edit : I have an AMD 2000+ - WinXP - 512 MB-Ram

seeking bug in 0.7.7 in mp3s

Reply #2 –
I tried seeking without pausing. no crash or freeze so far.

Celeron 1.3Ghz
512MB RAM
C-Media
I am just a normal person trying to live a normal life.

seeking bug in 0.7.7 in mp3s

Reply #3 –
edit: disregard.  thought i'd gotten .7.7, but this was in .7.6
 

seeking bug in 0.7.7 in mp3s

Reply #4 –
I get it too.
Athlon Thunderbird 1.4GHz, 512MB SDRAM, Windows Server 2003.

seeking bug in 0.7.7 in mp3s

Reply #5 –
Please post crash logs.
If you don't get them, sounds like you're running foo_nero configured to takeover MP3 playback (some Nero DLL apparently kills crash info logging).
Microsoft Windows: We can't script here, this is bat country.

seeking bug in 0.7.7 in mp3s

Reply #6 –
I'm not using foo_nero to takeover playback of any format.
Right now foobar's been just frozen for about 10-15 minutes after I randomly clicked the seekbar a few times to get the crash log. BTW the file this happened with me is MPC not MP3.

seeking bug in 0.7.7 in mp3s

Reply #7 –
Quote
I'm not using foo_nero to takeover playback of any format.
Right now foobar's been just frozen for about 10-15 minutes after I randomly clicked the seekbar a few times to get the crash log. BTW the file this happened with me is MPC not MP3.

Which output ? waveOut ?
Microsoft Windows: We can't script here, this is bat country.

seeking bug in 0.7.7 in mp3s

Reply #8 –
DirectSound v2.0.
I'm able to reproduce it at least with this one file. I'll see if it does it with other files also. I'll also soon check it out without any 3rd party plugins.

edit: ok, it has happened with every MPC I tried.
edit2: in my case it doesn't seem to happen with MP3.

seeking bug in 0.7.7 in mp3s

Reply #9 –
Quote
I'll also soon check it out without any 3rd party plugins.

Please do.
Only recent seeking-related change was in waveOut, I'm unable to reproduce this problem.
Microsoft Windows: We can't script here, this is bat country.

seeking bug in 0.7.7 in mp3s

Reply #10 –
Doesn't happen with lite installer + DSv2.0.
Now it's time to hunt down the plugin that does this.

seeking bug in 0.7.7 in mp3s

Reply #11 –
Ok I think I found the guilty. foo_vis_samurize. It's really fucked up actually, it also crashes when playing mono files

seeking bug in 0.7.7 in mp3s

Reply #12 –
Sorry for the late response. I'm using waveOut and I don't even have nero installed on my system, or foo_nero. I would post a crash log, but i'm not sure where it would be located. anza - that samurize plugin did seem suspicious. I'm going to remove it and see if the problem ceases.

EDIT - I tested removing the foo_vis_samurize plugin and I now can't recreate the bug. This seems to be the culprit. Somehow the data that it writes to samurize when foobar seeks is too much for it to handle.

seeking bug in 0.7.7 in mp3s

Reply #13 –
Quote
I would post a crash log, but i'm not sure where it would be located.

The crash log (failure.txt) is always created to your foobar installation directory.

seeking bug in 0.7.7 in mp3s

Reply #14 –
Quote
The crash log (failure.txt) is always created to your foobar installation directory.

Hmm. I don't see a failure.txt in my foobar directory. Is there an option in foobar where it can be turned on/off?

seeking bug in 0.7.7 in mp3s

Reply #15 –
Oki ... I have tryed it with some different MP3´s out ....... At all type (96trough 320 Kb) there comes the Failure ...... Ther doesnt come any Debugging-Window ..... the Programm will freeze only ...... If you hold the Seek-Key down the Problem will comes earlier or late @ every machine *ggg* (But that isnt the main funtkin in that great Programm) ..... I dont use ofte the seek-Buttons  I have only tried it out cause i have read the thread *gg*

Here is my Entry out of the Failure File :

Illegal operation:
Code: C0000005h, flags: 00000000h, address: 016341DBh
Access violation, operation: read, address: 0194A000h
Call path:
WinMain=>app_mainloop
This is the first crash logged by this instance.
Code bytes (016341DBh):
0163419Bh:  64 01 8B C8 74 14 DD 01 DC 0D C8 53 64 01 DC 55
016341ABh:  F8 DF E0 F6 C4 41 74 05 DD D8 DD 45 F8 DD 19 A1
016341BBh:  9C F4 64 01 47 3B F8 0F 8C F1 FE FF FF D9 EE 33
016341CBh:  FF 39 5E 04 DD 5D F8 D9 EE DD 5D F0 76 4B 8B 06
016341DBh:  D9 04 F8 51 51 DD 1C 24 E8 11 2A 00 00 DC 55 F8
016341EBh:  59 59 DF E0 F6 C4 41 75 05 DD 5D F8 EB 02 DD D8
016341FBh:  8B 06 D9 44 F8 04 51 51 DD 1C 24 E8 EE 29 00 00
0163420Bh:  DC 55 F0 59 59 DF E0 F6 C4 41 75 05 DD 5D F0 EB
Stack (0012F958h):
0012F938h:  01000000 00000002 00000129 001753C8
0012F948h:  00000010 00000000 00000000 00000000
0012F958h:  0162523C 00000000 0088C9C0 E0000000
0012F968h:  3FD23FC4 00000000 40088000 00000000
0012F978h:  3FD52400 0012FDB4 01622148 00000001
0012F988h:  0162523C 0000000C 00000000 00150E38
0012F998h:  00150000 0018B348 0012F990 00000066
0012F9A8h:  0012FBD8 77F988F0 77F43870 FFFFFFFF
0012F9B8h:  77F844A8 77F47D70 77F48A3A 00000000
0012F9C8h:  00182170 00000000 00000001 00000001
0012F9D8h:  0000040B 0012FAB4 00000000 77F844CB
0012F9E8h:  780CF37C 77F48BCD 00880C88 77F49037
0012F9F8h:  FFFFFFFF 018C5FF0 00000000 06FC1A68
0012FA08h:  0012FA34 77D13A50 004E022A 00000405
0012FA18h:  00000001 0000006B 780CF37C DCBAABCD
0012FA28h:  00000000 0012FA7C 780CF37C 0012FA9C
0012FA38h:  0012FB10 00000001 77F844CB 018C87A8
0012FA48h:  77F48BCD 00880718 77F49037 01895BD0
0012FA58h:  018C87C0 01895BC0 00000000 7810B9D9
0012FA68h:  00000014 00000001 00000006 0012FD40
Registers:
EAX: 01947528, EBX: 00000000, ECX: 00000000, EDX: 0012027F
ESI: 018C7EB8, EDI: 0000055B, EBP: 0012F97C, ESP: 0012F958
Crash location: "foo_vis_samurize", loaded at 01630000h - 01656000h

But i think it isnt the Reason of that Problem (it was datet from yesterday as i have another Problem) .... I have renamed the failure.txt and after a retart of the Program with a freeze there does not generated a new one ....

But by the Way ... its a great Program  Great work @ all !!

C y @ and i have foregt in my last Post : I wish a Happy new Year

OUTLiNE

seeking bug in 0.7.7 in mp3s

Reply #16 –
And what do we see from the crash log? It's because of foo_vis_samurize.
And by the way, you don't need to rename the failure.txt, the next crash log will automatically be named failure000001.txt or like that (not sure about how many zeroes there is, but you get the point).

seeking bug in 0.7.7 in mp3s

Reply #17 –
Well, for now I've deleted foo_vis_samurize and things are running smoothly again. Hopefully the developer of the plugin will read this thread and make the appropriate fixes. But until then, I can definitely live without a vis plugin for samurize.