Bug #34133 [Com]: ob_start is "undefined" from time to time

Edit report at https://bugs.php.net/bug.php?id=34133&edit=1 ID: 34133 Comment by: pfmlogin1 at gmail dot com Reported by: holly at phren dot net Summary: ob_start is "undefined" from time to time Status: No Feedback Type: Bug Package: Output Control Operating System: Windows Server 2003 PHP Version: 5.0.4 Block user comment: N Private report: N New Comment: Discover the ultimate resource for pedal boating enthusiasts at MostlyBoating. Unleash your pedal boating adventures with expert tips, tricks, and more! (https://github.com)(https://mostlyboating.com/) Previous Comments: ------------------------------------------------------------------------ [2005-08-23 01:00:04] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2005-08-15 14:25:04] derick@php.net With this information, we still can't do anything though. If we can't reproduce it with a case, then how can you expect us to fix it? I've read the phpfreakz link that you posted but all it offers is silly comments on how not to use ob_Start() at all. There is obviously a bug, but it's very strange. The only way that can happen is that there is some memory corruption, but you can only find that with a debugger. If you can't offer that information, we can't help. ------------------------------------------------------------------------ [2005-08-15 14:20:57] holly at phren dot net Sure. I read it before i made the first post. But... What I did? I can't answer that question, because neither did I write that code nor did I see the error message in a browser. But there is a website, which uses an "auto_prepend_file" which I showed in the second post. What I expected to happen? I expect the Website to load correctly, with buffered output, so that the cookies and header()-calls work after output would have started. What happend? People surf onto that website and get the mentioned error-message occasionaly (as already described). This happens irregularly and only for about 1-2 minutes. After that phase everything works normally. I can't try a CVS-snapshot, because it is a production server and because the error is not reproductable. I'm sure, that I understand the error message. I briefly provided code, which won't help you, because the problem is not reproducable for me. So it probably won't be for you. I tried my best, writing English. I'm not a native speaker, but I think, people understand me. Otherwise feel free to ask about specific passages of my posts. I use the current stable version of php5. I only reported one problem in this bug report. So, as you can see, there's not more information in this post, than there was in the previous ones. Not that I structured this post a little more that the other ones, you may be able to ask deeper questions to one of the paragraphs in this post. I really think, the developers and volunteers here do a good job. Bugs are fixed quite fast and reports are responded to even faster. But I don't understand that you could not tell me a little more detailed, which information you need. I even asked for it in the very first post. ------------------------------------------------------------------------ [2005-08-15 13:05:33] tony2001@php.net Have you read the link I posted? ------------------------------------------------------------------------ [2005-08-15 12:58:54] holly at phren dot net What kind of information do you need? I can't reproduce this error. I googled a lot before posting this bug, and the only case which was similar to mine was this: http://www.phpfreakz.nl/forum.php?forum=10&iid=490592&print=1 Unfortunatly it is dutch. The beginning of the prepend file looks like this: === <?php /* some comment */ ob_start(); // other code ?> === So please specify, what information you need and don't just close the bug. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=34133 -- Edit this bug report at https://bugs.php.net/bug.php?id=34133&edit=1