After installing the views module I noticed my disk usage jumped to over 1GB. I checked my site and noticed these files that were created right after installing the views module:

public_html/core.29113 73.45 Meg
public_html/core.7535 73.20 Meg
public_html/core.1142 73.19 Meg
public_html/core.29719 73.06 Meg
public_html/core.7801 72.94 Meg
public_html/core.30192 72.54 Meg
public_html/core.30214 72.41 Meg
public_html/core.1042 71.91 Meg
public_html/core.24833 71.64 Meg
public_html/core.24910 71.64 Meg
public_html/core.29163 71.00 Meg
public_html/core.28268 70.97 Meg
public_html/core.28425 70.87 Meg

Are these created by the views module or Drupal?

Comments

michelle’s picture

Since I happened to be on IRC with the views maintainer, I asked him quick:

"That's a core file -- meaning something segfaulted. Probably apache. Views doesn't produce that file naturally. PHP can cause apache to segfault when references get crazy."

So those aren't normally occurring files. Thank goodness or I'd run out of space pretty fast on my shared hosting. :)

Michelle

--------------------------------------
My site: http://shellmultimedia.com

styro’s picture

Those files are a memory dump of the Apache process that crashed. Useful for Apache (or mod_php etc) programmers debugging their code, but not really any use for anybody else.

http://en.wikipedia.org/wiki/Core_dump

--
Anton
New to Drupal? | Troubleshooting FAQ
Example knowledge base built with Drupal

TurtleX’s picture

So these definitely are not Drupal or Views module related?

Would it be safe to delete these?

styro’s picture

Drupal via the Views module may be inadvertantly triggering (via not robust enough code in PHP) the crashes that create them, so they are related in that way. But they are unrelated in so far as Drupal won't be able to use them for anything.

Deleting them won't affect your site at all. But it would preferable to fix whatever is causing them.

--
Anton
New to Drupal? | Troubleshooting FAQ
Example knowledge base built with Drupal

TurtleX’s picture

Thanks, I just contacted my host and they said it a script I am running on my site. I'd like to know what caused this as well.

Initially, I had some trouble getting the views module to work, maybe that's it. It works fine now though.